a ÝŒxd¨ã@s|ddlmZmZddlmZddlmZmZmZm Z m Z m Z m Z m Z ddlZddlmZmZdgZejZGdd„deƒZdS)é)ÚAbstractAsyncContextManagerÚasynccontextmanager)Ú TracebackType)ÚAnyÚAsyncGeneratorÚ AwaitableÚCallableÚDictÚOptionalÚTupleÚTypeN)Ú EventEmitterÚ PyeeExceptionÚTrioEventEmittercsÊeZdZdZdeddœ‡fdd„ Zeeedfe e efege dfdœd d „Z eeedfe e efddœd d „Z eed dœdd„ƒZddœdd„Zeeeeeeeeedœdd„Z‡ZS)ra„An event emitter class which can run trio tasks in a trio nursery. By default, this class will lazily create both a nursery manager (the object returned from ``trio.open_nursery()`` and a nursery (the object yielded by using the nursery manager as an async context manager). It is also possible to supply an existing nursery manager via the ``manager`` argument, or an existing nursery via the ``nursery`` argument. Instances of TrioEventEmitter are themselves async context managers, so that they may manage the lifecycle of the underlying trio nursery. For example, typical usage of this library may look something like this:: async with TrioEventEmitter() as ee: # Underlying nursery is instantiated and ready to go @ee.on('data') async def handler(data): print(data) ee.emit('event') # Underlying nursery and manager have been cleaned up Unlike the case with the EventEmitter, all exceptions raised by event handlers are automatically emitted on the ``error`` event. This is important for trio coroutines specifically but is also handled for synchronous functions for consistency. For trio coroutine event handlers, calling emit is non-blocking. In other words, you should not attempt to await emit; the coroutine is scheduled in a fire-and-forget fashion. Nz)AbstractAsyncContextManager[trio.Nursery])ÚnurseryÚmanagercsLtt|ƒ ¡d|_d|_|r2|r*tdƒ‚||_n|r>||_n t ¡|_dS)Nz?You may either pass a nursery or a nursery manager but not both)ÚsuperrÚ__init__Ú_nurseryÚ_managerrÚtrioZ open_nursery)Úselfrr©Ú __class__©úA/var/www/html/Ranjet/env/lib/python3.9/site-packages/pyee/trio.pyr2sÿzTrioEventEmitter.__init__.)ÚfÚargsÚkwargsÚreturncsddœ‡‡‡‡fdd„ }|S)N©rc “sNzˆˆiˆ¤ŽIdHWn0tyH}zˆ d|¡WYd}~n d}~00dS)NÚerror)Ú ExceptionÚemit)Úexc©rrrrrrÚrunnerKsz.TrioEventEmitter._async_runner..runnerr)rrrrr&rr%rÚ _async_runnerEszTrioEventEmitter._async_runnercCs(|jstdƒ‚|j | |||¡¡dS)NzUninitialized trio nursery)rrZ start_soonr')rrrrrrrÚ _emit_runSszTrioEventEmitter._emit_run)rNr c Csp|jdur|VnZ|jdurd|j4IdHš"}||_|VWdƒIdHql1IdHsX0Yntdƒ‚dS)a Returns an async contextmanager which manages the underlying nursery to the EventEmitter. The ``TrioEventEmitter``'s async context management methods are implemented using this function, but it may also be used directly for clarity. Nz(Uninitialized nursery or nursery manager)rrr)rrrrrÚcontext]s  2zTrioEventEmitter.contextcÃs| ¡|_|j ¡IdHS)N)r)Ú_contextÚ __aenter__)rrrrr+osþzTrioEventEmitter.__aenter__)ÚtypeÚvalueÚ tracebackrcÃs>|jdurtdƒ‚|j |||¡IdH}d|_d|_d|_|S)Nz(Attempting to exit uninitialized context)r*rÚ __aexit__rr)rr,r-r.Úrvrrrr/us zTrioEventEmitter.__aexit__)NN)Ú__name__Ú __module__Ú __qualname__Ú__doc__ÚNurseryrrr rr Ústrrr'r(rrr)r+r r Ú BaseExceptionrÚboolr/Ú __classcell__rrrrrs4"ýý  û   û þ û)Ú contextlibrrÚtypesrÚtypingrrrrr r r r rZ pyee.baser rÚ__all__r5rrrrrÚs (