h@SrSSKJr SSKrSSKJrJr "SS5rg)zWin32 compatibility utilities.) annotationsN)AnyCallablec8\rSrSrSrS S SjjrSrSrSrSr g) allow_interrupt aUtility for fixing CTRL-C events on Windows. On Windows, the Python interpreter intercepts CTRL-C events in order to translate them into ``KeyboardInterrupt`` exceptions. It (presumably) does this by setting a flag in its "console control handler" and checking it later at a convenient location in the interpreter. However, when the Python interpreter is blocked waiting for the ZMQ poll operation to complete, it must wait for ZMQ's ``select()`` operation to complete before translating the CTRL-C event into the ``KeyboardInterrupt`` exception. The only way to fix this seems to be to add our own "console control handler" and perform some application-defined operation that will unblock the ZMQ polling operation in order to force ZMQ to pass control back to the Python interpreter. This context manager performs all that Windows-y stuff, providing you with a hook that is called when a CTRL-C event is intercepted. This hook allows you to unblock your ZMQ poll operation immediately, which will then result in the expected ``KeyboardInterrupt`` exception. Without this context manager, your ZMQ-based application will not respond normally to CTRL-C events on Windows. If a CTRL-C event occurs while blocked on ZMQ socket polling, the translation to a ``KeyboardInterrupt`` exception will be delayed until the I/O completes and control returns to the Python interpreter (this may never happen if you use an infinite timeout). A no-op implementation is provided on non-Win32 systems to avoid the application from having to conditionally use it. Example usage: .. sourcecode:: python def stop_my_application(): # ... with allow_interrupt(stop_my_application): # main polling loop. In a typical ZMQ application, you would use the "self pipe trick" to send message to a ``PAIR`` socket in order to interrupt your blocking socket polling operation. In a Tornado event loop, you can use the ``IOLoop.stop`` method to unblock your I/O loop. NcP[RS:wagURU5 g)zTranslate ``action`` into a CTRL-C handler. ``action`` is a callable that takes no arguments and returns no value (returned value is ignored). It must *NEVER* raise an exception. If unspecified, a no-op will be used. ntN)osname _init_action)selfactions bC:\Users\julio\OneDrive\Documentos\Trabajo\Ideas Frescas\venv\Lib\site-packages\zmq/utils/win32.py__init__allow_interrupt.__init__@s  77d?  &!c^SSKJnJn SSKJnJn UR S5nU"XE5nUR=olXt4Ul XHl TcSmTUl UU4Sj5n Xl g)Nr) WINFUNCTYPEwindll)BOOLDWORDkernel32cgNrrrr,allow_interrupt._init_action..action]src >US:XaT"5 g)Nrr)eventrs rhandle,allow_interrupt._init_action..handlebszr) ctypesrrctypes.wintypesrr LoadLibrarySetConsoleCtrlHandler_SetConsoleCtrlHandlerargtypesrestyperr ) rrrrrrrPHANDLER_ROUTINEr%r s ` rr allow_interrupt._init_actionMsz./%%j1't3  * *  ;+;)A&(,% >      rc[RS:wagURURS5nUS:Xa [ 5eg)z"Install the custom CTRL-C handler.r Nrr r r&r OSError)rresults r __enter__allow_interrupt.__enter__p; 77d? ,,T[[!< Q;)O rc[RS:wagURURS5nUS:Xa [ 5eg)z!Remove the custom CTRL-C handler.r Nrr-)rargsr/s r__exit__allow_interrupt.__exit__zr2r)r&rr r)rzCallable[[], Any] | NonereturnNone) __name__ __module__ __qualname____firstlineno____doc__rr r0r5__static_attributes__rrrrr s0d "!Frr)r= __future__rr typingrrrrrrrAs$ # uur