관리-도구
편집 파일: base_events.cpython-312.pyc
� �Q�fk0 � �> � d Z ddlZddlZddlZddlZddlZddlZddlZddl Z ddl Z ddlZddlZddl Z ddlZddlZddlZddlZddlZ ddlZddlmZ ddlmZ ddlmZ ddlmZ ddlmZ dd lmZ dd lmZ ddlmZ ddlmZ dd lmZ ddlm Z ddlm!Z! ddl"m#Z# dZ$dZ%dZ& e'e d� Z(dZ)d� Z*d� Z+d� Z,d&d�Z-d'd�Z.d� Z/ e'e d� rd� Z0nd� Z0d� Z1 G d � d!ejd � Z3 G d"� d#ejh � Z5 G d$� d%ejl � Z7y# e$ r dZY ��w xY w)(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. � N� )� constants)� coroutines)�events)� exceptions)�futures)� protocols)�sslproto)� staggered)�tasks)�timeouts)� transports)�trsock)�logger)� BaseEventLoop�Server�d g �?�AF_INET6i�Q c � � | j }t t |dd � t j � rt |j � S t | � S )N�__self__)� _callback� isinstance�getattrr �Task�reprr �str)�handle�cbs �:/opt/alt/python312/lib64/python3.12/asyncio/base_events.py�_format_handler H s= � � � � �B��'�"�j�$�/����<��B�K�K� � ��6�{�� c �h � | t j k( ry| t j k( ryt | � S )Nz<pipe>z<stdout>)� subprocess�PIPE�STDOUTr )�fds r �_format_piper'