*j= F S r SSKrSSKrSSKrSSKrSSKrSSKrSSKrSSK r SSK
r
SSKrSSKrSSK
r
SSKrSSKrSSKrSSKr SSKrSSKJr SSKJr SSKJr SSKJr SSKJr SS KJr SS
KJr SSKJr SSKJr SS
KJr SSKJr SSKJ r SSK!J"r" Sr#Sr$Sr%\&" \ S5 r'Sr(S r)S r*S r+S&S jr,S'S jr-S r.\&" \ S5 ( a S r/OS r/S r0 " S S!\Rb 5 r2 " S" S#\Rf 5 r4 " S$ S%\Rj 5 r6g! \ a Sr Nf = f)(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)
BaseEventLoopServerd g ?AF_INET6iQ c U R n[ [ USS 5 [ R 5 ( a [ UR 5 $ [ U 5 $ )N__self__) _callback
isinstancegetattrr Taskreprr str)handlecbs :/opt/alt/python313/lib64/python3.13/asyncio/base_events.py_format_handler G s@ B'"j$/<<BKK 6{ c l U [ R :X a gU [ R :X a g[ U 5 $ )Nz