gxUddlmZddlmZmZmZmZmZmZm Z m Z ddl Z ddl m Z ddlmZe deZeZeeegdffed<d ed dfd Zd ed ededed df dZeddddZeeeeeffed<e e de de dfZe e de de de dfZ d"deededededed ed efd!Zy)#)wraps)AnyCallableDictOptionalTupleTypeTypeVarUnionN)Literal) EventEmitterUpliftingEventEmitter)bound EMIT_WRAPPERS event_emitterreturnc0|tvrt|yy)zAUnwrap an uplifted EventEmitter, returning it to its prior state.N)r)rs @/var/www/openai/venv/lib/python3.12/site-packages/pyee/uplift.pyunwraprs %m$&&leftright error_handlerproxy_new_listenerc jtjtdtdt dt dt ffd }dfd }dfd }|_|t<|_y) Neventargskwargsrcj|||}s|dk7r j|||}nd}|xs|}|sj||r|dnd|S)N new_listenerFr)_call_handlers_emit_handle_potential_error) rrr left_handled right_handledhandledrrrrs r wrapped_emitz_wrap..wrapped_emit si!00fE  .!8!00fEM!M/-  6 6ud1gSW XrcXtjtdty)NzjPatched ee.unwrap() is deprecated and will be removed in a future release. Use pyee.uplift.unwrap instead.)warningswarnDeprecationWarningr)rsr_unwrapz_wrap.._unwrap3s& B  t rcb_r t<n t=`_ty)N)emitrr)r left_emit left_unwraprsr unwrap_hookz_wrap..unwrap_hook<s2 "-M$ d#  u r)rN)r-rgetrstrrboolr) rrrrr&r+r0r.r/s ```` @@r_wrapr4sz  I0=0A0A$0GK 9Cst$  DI%M$DKr)FT)TF)TT)FF)forwardbackwardbothneither_PROXY_NEW_LISTENER_SETTINGSnew underlyingr8r5r6r7clserror_handlingrrct|\}}||i|}t||f||f||f} | |\} } t||| |t||| ||S)ap A helper to create instances of an event emitter `cls` that inherits event behavior from an `underlying` event emitter instance. This is mostly helpful if you have a simple underlying event emitter that you don't have direct control over, but you want to use that event emitter in a new context - for example, you may want to `uplift` a `EventEmitter` supplied by a third party library into an `AsyncIOEventEmitter` so that you may register async event handlers in your `asyncio` app but still be able to receive events from the underlying event emitter and call the underlying event emitter's existing handlers. When called, `uplift` instantiates a new instance of `cls`, passing along any unrecognized arguments, and overwrites the `emit` method on the `underlying` event emitter to also emit events on the new event emitter and vice versa. In both cases, they return whether the `emit` method was handled by either emitter. Execution order prefers the event emitter on which `emit` was called. The `unwrap` function may be called on either instance; this will unwrap both `emit` methods. The `error_handling` flag can be configured to control what happens to unhandled errors: - 'new': Error handling for the new event emitter is always used and the underlying library's non-event-based error handling is inert. - 'underlying': Error handling on the underlying event emitter is always used and the new event emitter can not implement non-event-based error handling. - 'neither': Error handling for the new event emitter is used if the handler was registered on the new event emitter, and vice versa. Tuning this option can be useful depending on how the underlying event emitter does error handling. The default is 'new'. The `proxy_new_listener` option can be configured to control how `new_listener` events are treated: - 'forward': `new_listener` events are propagated from the underlying event emitter to the new event emitter but not vice versa. - 'both': `new_listener` events are propagated as with other events. - 'neither': `new_listener` events are only fired on their respective event emitters. - 'backward': `new_listener` events are propagated from the new event emitter to the underlying event emitter, but not vice versa. Tuning this option can be useful depending on how the `new_listener` event is used by the underlying event emitter, if at all. The default is 'forward', since `underlying` may not know how to handle certain handlers, such as asyncio coroutines. Each event emitter tracks its own internal table of handlers. `remove_listener`, `remove_all_listeners` and `listeners` all work independently. This means you will have to remember which event emitter an event handler was added to! Note that both the new event emitter returned by `cls` and the underlying event emitter should inherit from `EventEmitter`, or at least implement the interface for the undocumented `_call_handlers` and `_emit_handle_potential_error` methods. )r:r;r8)r9dictr4) r<r;r=rrrnew_proxy_new_listenerunderlying_proxy_new_listenerr:uplift_error_handlersnew_error_handlerunderlying_error_handlers rupliftrE[sT %%78%"%d!5f!5CJN #JJ #;c:EVK3H2W// #z,.DE *c35RS Jr)r:r5) functoolsrtypingrrrrrr r r r(typing_extensionsr pyee.baser rr?r__annotations__rr3r4r9r2 ErrorStrategy ProxyStrategyrErrrNsmMMM%" 7|L9= tL(2t8"445>','4' 3 3 33 3  3l>B     >d3dDj(9#9:gengl&;WY=OOP  I +WV_gi>PP %*(1 W # $WW"W& W  W  WWr