B
ú?ÂCúG;ã @ s° d Z ddlZddlZddlZddlZddlZddlZddlZddl Z ddl
Z
ddlZddlZddl
Z
ddlZddlZddlZyddlZW n ek
r dZY nX ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ dd lmZ dd
lmZ ddlmZ ddlmZ d
ZdZdZ e!e dƒZ"dZ#e$ƒ Z%dd„ Z&dd„ Z'dd„ Z(d&dd„Z)dd„ Z*e!e dƒrndd„ Z+ndd„ Z+G d d!„ d!ej,ƒZ-G d"d#„ d#ej.ƒZ/G d$d%„ d%ej0ƒZ1dS )'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)Úfutures)Ú protocols)Ússlproto)Útasks)Ú
transports)Úlogger)Ú
BaseEventLoopéd g à?ÚAF_INET6i€Q c C s0 | j }tt|dd ƒtjƒr$t|jƒS t| ƒS d S )NÚ__self__)Z _callbackÚ
isinstanceÚgetattrr ÚTaskÚreprr Ústr)ÚhandleÚcb© r ú8/opt/alt/python37/lib64/python3.7/asyncio/base_events.pyÚ_format_handleE s
r c C s( | t jkrdS | t jkrdS t| ƒS d S )Nz