Файловый менеджер - Редактировать - /opt/imh-python/lib/python3.9/site-packages/zmq/utils/__pycache__/win32.cpython-39.pyc
Ðазад
a a�h � @ s� d Z ddlZG dd� de�Zejdkr�ddlmZmZ ddlm Z m Z e� d�Z ee e �Z e jZe e fe_e e_G d d � d e�ZnG d d � d e�ZdS ) z Win32 compatibility utilities.� Nc @ s2 e Zd ZdZd dd�Zdd� Zdd� Zd d � ZdS ) �_allow_interruptaD Utility 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. Nc C s | � |� dS )a 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)� _init_action��self�action� r �/root/rpmbuild/BUILDROOT/imh-python39-modules-3.9.7-92.el8.x86_64/opt/imh-python/lib/python3.9/site-packages/zmq/utils/win32.py�__init__> s z_allow_interrupt.__init__c C s d S �Nr r r r r r I s z _allow_interrupt._init_actionc C s | S r r )r r r r � __enter__L s z_allow_interrupt.__enter__c G s d S r r )r �argsr r r �__exit__O s z_allow_interrupt.__exit__)N)�__name__� __module__� __qualname__�__doc__r r r r r r r r r s 2 r �nt)� WINFUNCTYPE�windll)�BOOL�DWORD�kernel32c @ s* e Zd ZejZdd� Zdd� Zdd� ZdS )�allow_interruptc s0 � d u rdd� � � | _ t� fdd��}|| _d S )Nc S s d S r r r r r r �<lambda>c � z.allow_interrupt._init_action.<locals>.<lambda>c s | dkr� � dS )Nr r )�event�r r r �handlee s z,allow_interrupt._init_action.<locals>.handle)r �PHANDLER_ROUTINEr )r r r r r r r a s z allow_interrupt._init_actionc C s t | jd�}|dkrt� �dS )z"Install the custom CTRL-C handler.� r N��SetConsoleCtrlHandlerr Z WindowsError)r �resultr r r r r s zallow_interrupt.__enter__c G s t | jd�}|dkrt� �dS )z!Remove the custom CTRL-C handler.r Nr )r r r" r r r r z s zallow_interrupt.__exit__N)r r r r r r r r r r r r r ^ s r c @ s e Zd ZejZdS )r N)r r r r r r r r r r � s )r �os�objectr �name�ctypesr r Zctypes.wintypesr r Z LoadLibraryr r r! �argtypes�restyper r r r r �<module> s G $
| ver. 1.1 | |
.
| PHP 8.3.30 | Ð“ÐµÐ½ÐµÑ€Ð°Ñ†Ð¸Ñ Ñтраницы: 0 |
proxy
|
phpinfo
|
ÐаÑтройка