| Server IP : 121.121.20.254 / Your IP : 216.73.217.51 Web Server : Microsoft-IIS/10.0 System : Windows NT WEB-SERVER 10.0 build 20348 (Windows Server 2022) AMD64 User : IUSR ( 0) PHP Version : 8.3.28 Disable Function : NONE MySQL : ON | cURL : ON | WGET : OFF | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : C:/Python315/Lib/asyncio/__pycache__/ |
Upload File : |
R
>lqj�G c �^ � Q s ] PHs] PHs] PHs] PHs] PHs] PHs] PH s] PH$s ] PH(s
] PH,s] PH0s] PH4s
] PH8s] PH<s] PH@s] PHDs] PHHs] PHLs ] PHRs]QHXGs ]QHXGs ]QHXGs ]QHXGs ]QHXGs ]QHXGs ]QHXGs ]QHXGs ]Q HXGs ]Q
HXG s ]QHXG!s! ]QHXG"s" ]Q
H�G$s$ Q s%]ds&Qs'\( \Q2 s)Q!s*Q s+Q s,Q s-Q"Q ks.Q#Q ks/Q s0\( \Q2 % c Q s1LQ s1Q s2 Q Q\Of 2 s4 Q Q\Oj 2 s6 Q Q\On 2 s8P! \ c Ps K�h 9 h)$a� Base implementation of event loop.
The event loop can be broken up into a multiplexer (the part
responsible for notifying us of I/O events) and the event loop proper,
which wraps a multiplexer with functionality for scheduling callbacks,
immediately or at a given time in the future.
Whenever a public API takes a callback, subsequent positional
arguments will be passed to the callback if/when it is called. This
avoids the proliferation of trivial lambdas implementing closures.
Keyword arguments for the callback are not supported; this is a
conscious design decision, leaving the door open for keyword arguments
to modify the meaning of the API call itself.
)� constants)�
coroutines)�events)�
exceptions)�futures)� protocols)�sslproto)� staggered)�tasks)�timeouts)�
transports)�trsock)�logger�
BaseEventLoop�Serverg �?�AF_INET6c � � U O o[ [ UQ P2 [ O 2 % c [ UO 2 ! [ U 2 ! )�__self__)� _callback�
isinstance�getattrr �Task�reprr �str)�handle�cbs & �(C:\Python315\\Lib\asyncio\base_events.py�_format_handler I s@ � � � � �B��'�"�j�$�/����<�<��B�K�K� � ��6�{�� c �v � U [ O 6X c Q ! U [ O 6X c Q! [ U 2 ! )z<pipe>z<stdout>)�
subprocess�PIPE�STDOUTr )�fds &r �_format_piper# R s+ � � �Z�_�_��� �z� � � ���B�x�r c �� � [ [ Q 2 % f [ Q2 g U O [ O [ O
]2 P! [ c
[ Q2 gh 9 h)�SO_REUSEPORTz)reuse_port not supported by socket modulezTreuse_port not supported by socket module, SO_REUSEPORT defined but not implemented.)�hasattr�socket�
ValueError�
setsockopt�
SOL_SOCKETr% �OSError��socks &r �_set_reuseportr. [ sc � ��6�>�*�*��D�E�E� J��O�O�F�-�-�v�/B�/B�A�F��� J�� I� J�
J� J�s �/A � A,�
A,c
�� � [ [ Q 2 % f P! U] [ O [ O .7 f U e P! U[ O 6X c [ O oL(U[ O
6X c [ O oLP! Ue ] oLL[
U[ 2 % c UQ6X c ] oL,[
U[ 2 % c UP6X c ] oL [ U2 oU[ O 6X c>