ó L]c@sÕdZddlZdefd„ƒYZejdkr»ddlmZmZddlm Z m Z ej dƒZ ee e ƒZ e jZe e fe_e e_d efd „ƒYZnd efd „ƒYZdS( sWin32 compatibility utilities.iÿÿÿÿNt_allow_interruptcBs5eZdZdd„Zd„Zd„Zd„ZRS(sDUtility 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. cCs|j|ƒdS(s Translate ``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. N(t _init_action(tselftaction((s.lib/python2.7/site-packages/zmq/utils/win32.pyt__init__>s cCsdS(N((RR((s.lib/python2.7/site-packages/zmq/utils/win32.pyRIscCs|S(N((R((s.lib/python2.7/site-packages/zmq/utils/win32.pyt __enter__LscGsdS(N((Rtargs((s.lib/python2.7/site-packages/zmq/utils/win32.pyt__exit__OsN(t__name__t __module__t__doc__tNoneRRRR(((s.lib/python2.7/site-packages/zmq/utils/win32.pyR s 1  tnt(t WINFUNCTYPEtwindll(tBOOLtDWORDtkernel32tallow_interruptcBs,eZejZd„Zd„Zd„ZRS(csCˆdkrd„‰nˆ|_t‡fd†ƒ}||_dS(NcSsdS(N(R (((s.lib/python2.7/site-packages/zmq/utils/win32.pytctcs|dkrˆƒndS(Ni((tevent(R(s.lib/python2.7/site-packages/zmq/utils/win32.pythandlees  (R RtPHANDLER_ROUTINER(RRR((Rs.lib/python2.7/site-packages/zmq/utils/win32.pyRas     cCs.t|jdƒ}|dkr*tƒ‚ndS(s"Install the custom CTRL-C handler.iiN(tSetConsoleCtrlHandlerRt WindowsError(Rtresult((s.lib/python2.7/site-packages/zmq/utils/win32.pyRrs cGs.t|jdƒ}|dkr*tƒ‚ndS(s!Remove the custom CTRL-C handler.iN(RRR(RRR((s.lib/python2.7/site-packages/zmq/utils/win32.pyRzs (RR RR RRR(((s.lib/python2.7/site-packages/zmq/utils/win32.pyR^s   cBseZejZRS((RR RR (((s.lib/python2.7/site-packages/zmq/utils/win32.pyR‚s (R tostobjectRtnametctypesR Rtctypes.wintypesRRt LoadLibraryRRRtargtypestrestypeR(((s.lib/python2.7/site-packages/zmq/utils/win32.pyts G  $