python (3.12.0)
ˑe) * d Z ddlZddlZddlZddlZddlZddlZddlZddl Z ddl
Z
ddlZddlZddl
Z
ddlZddlZddlZddlZ ddlZddlmZ ddlmZ ddlmZ ddlmZ ddlmZ dd lmZ dd
lmZ ddlmZ ddlmZ dd
lmZ ddlmZ ddl m!Z! dZ"dZ#dZ$ e%e d Z&dZ'd Z(d Z)d Z*d%dZ+d&dZ,d Z- e%e d rd Z.nd Z.d Z/ G d d ej` Z1 G d! d"ejd Z3 G d# d$ejh Z5y# 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)
transports)trsock)logger)
BaseEventLoopServerd g ?AF_INET6iQ c | j }t t |dd t j rt |j S t | S )N__self__) _callback
isinstancegetattrr Taskreprr str)handlecbs G/BuggyBox/python/3.12.0/bootstrap/lib/python3.12/asyncio/base_events.py_format_handler F s= B'"j$/<BKK 6{ c h | t j k( ry| t j k( ryt | S )Nz<pipe>z<stdout>)
subprocessPIPESTDOUTr )fds r _format_piper&