o i @s ddlmZGdddeZdS))osetc@s6eZdZdZifddZddZd ddZd d ZdS) EventManageraSpyne supports a simple event system that can be used to have repetitive boilerplate code that has to run for every method call nicely tucked away in one or more event handlers. The popular use-cases include things like database transaction management, logging and performance measurements. Various Spyne components support firing events at various stages during the request handling process, which are documented in the relevant classes. The events are stored in an ordered set. This means that the events are ran in the order they were added and adding a handler twice does not cause it to run twice. cCs||_t||_dS)awInitializer for the ``EventManager`` instance. :param parent: The owner of this event manager. As of Spyne 2.13, event managers can be owned by multiple objects, in which case this property will be none. :param handlers: A dict of event name (string)/callable pairs. The dict shallow-copied to the ``EventManager`` instance. N)parentdicthandlers)selfrrrK/var/www/html/LicenciasMIG/venv/lib/python3.10/site-packages/spyne/evmgr.py__init__&s zEventManager.__init__cCs(|j|t}||||j|<dS)a5Register a handler for the given event name. :param event_name: The event identifier, indicated by the documentation. Usually, this is a string. :param handler: A static python function that receives a single MethodContext argument. N)rgetradd)r event_namehandlerrrrr add_listener4s zEventManager.add_listenerNcCs(|dur |j|=dS|j||dSN)rremove)rr rrrr del_listenerAs zEventManager.del_listenercOs4|j|t}|D] }||g|Ri|q dS)aARun all the handlers for a given event name. :param event_name: The event identifier, indicated by the documentation. Usually, this is a string. :param ctx: The method context. Event-related data is conventionally stored in ctx.event attribute. N)rr r)rr ctxargskwargsrrrrr fire_eventHs zEventManager.fire_eventr)__name__ __module__ __qualname____doc__r rrrrrrr rs   rN)spyne.util.osetrobjectrrrrr s