o 0×¾g\ã@sždZddlmZddlmZddlmZddlmZdgZGdd„deƒZ Gdd „d e ƒZ Gd d „d e ƒZ Gd d „d e ƒZ Gdd„deƒZGdd„deƒZdS)z' Exceptions. .. versionadded:: 1.3b1 é)Úabsolute_import)Údivision)Úprint_function)Ú GreenletExitÚLoopExitc@s,eZdZdZedd„ƒZdd„Zdd„ZdS) ra† Exception thrown when the hub finishes running (`gevent.hub.Hub.run` would return). In a normal application, this is never thrown or caught explicitly. The internal implementation of functions like :meth:`gevent.hub.Hub.join` and :func:`gevent.joinall` may catch it, but user code generally should not. .. caution:: Errors in application programming can also lead to this exception being raised. Some examples include (but are not limited too): - greenlets deadlocking on a lock; - using a socket or other gevent object with native thread affinity from a different thread cCst|jƒdkr |jdSdS)z^ The (optional) hub that raised the error. .. versionadded:: 20.12.0 ééN)ÚlenÚargs©Úself©r ú[/var/www/html/backend_erp/backend_erp_env/lib/python3.10/site-packages/gevent/exceptions.pyÚhub(s ÿz LoopExit.hubcCsFt|jƒdkrddl}d|jd|jd| |jd¡fSt |¡S)Nrrz%s Hub: %s Handles: %sré)r r ÚpprintÚpformatÚ ExceptionÚ__repr__)r rr r rr3sýü zLoopExit.__repr__cCst|ƒS©N)Úreprr r r rÚ__str__BszLoopExit.__str__N)Ú__name__Ú __module__Ú __qualname__Ú__doc__Úpropertyrrrr r r rrs   c@óeZdZdZdS)ÚBlockingSwitchOutErrorz‘ Raised when a gevent synchronous function is called from a low-level event loop callback. This is usually a programming error. N©rrrrr r r rrEórc@r)ÚInvalidSwitchErrorzŸ Raised when the event loop returns control to a greenlet in an unexpected way. This is usually a bug in gevent, greenlet, or the event loop. Nrr r r rr!Nr r!c@r)ÚConcurrentObjectUseErrora- Raised when an object is used (waited on) by two greenlets independently, meaning the object was entered into a blocking state by one greenlet and then another while still blocking in the first one. This is usually a programming error. .. seealso:: `gevent.socket.wait` Nrr r r rr"Vr r"c@r)ÚInvalidThreadUseErrora— Raised when an object is used from a different thread than the one it is bound to. Some objects, such as gevent sockets, semaphores, and threadpools, are tightly bound to their hub and its loop. The hub and loop are not thread safe, with a few exceptions. Attempting to use such objects from a different thread is an error, and may cause problems ranging from incorrect results to memory corruption and a crashed process. In some cases, gevent catches this "accidentally", and the result is a `LoopExit`. In some cases, gevent doesn't catch this at all. In other cases (typically when the consequences are suspected to be more on the more severe end of the scale, and when the operation in question is already relatively heavyweight), gevent explicitly checks for this usage and will raise this exception when it is detected. .. versionadded:: 1.5a3 Nrr r r rr#br r#c@seZdZdZdd„ZdS)Ú HubDestroyeda  Internal exception, raised when we're trying to destroy the hub and we want the loop to stop running callbacks now. This must not be subclassed; the type is tested by identity. Clients outside of gevent must not raise this exception. .. versionadded:: 20.12.0 cCst ||¡||_dSr)rÚ__init__Ú destroy_loop)r r&r r rr%†s  zHubDestroyed.__init__N)rrrrr%r r r rr$zs r$N)rÚ __future__rrrÚgreenletrÚ__all__rrÚAssertionErrorrr!r"Ú RuntimeErrorr#r$r r r rÚs    ÿ1