Warning: session_start(): Session cannot be started after headers have already been sent in /home/tvrreohg/public_html/manga.php on line 13
§
àÀf„7 ã ó8 — d Z dZddlZddlZddlZddlZddlmZ ddl m
Z
ddl mZ ddl mZ dd l m
Z
e
j Ze
j Ze
j Ze
j Zej dz
Z G d
„ d¦ « ZeZd„ Zd
„ Zd„ Zd„ Zd„ Zd„ Zddœd„Z ddlZej xZZdS # e$ r Y dS w xY w)z.A Future class similar to the one in PEP 3148.)ÚFutureÚwrap_futureÚisfutureé N)ÚGenericAliasé )Úbase_futures)Úevents)Ú
exceptions)Úformat_helpersc óô — e Zd ZdZeZdZdZdZdZ dZ
dZdZdZ
ddœd„Zd„ Zd„ Z ee¦ « Zed„ ¦ « Zej d „ ¦ « Zd
„ Zd„ Zdd„Zd
„ Zd„ Zd„ Zd„ Zd„ Zddœd„Zd„ Z d„ Z!d„ Z"d„ Z#e#Z$dS )r a, This class is *almost* compatible with concurrent.futures.Future.
Differences:
- This class is not thread-safe.
- result() and exception() do not take a timeout argument and
raise an exception when the future isn't done yet.
- Callbacks registered with add_done_callback() are always called
via the event loop's call_soon().
- This class is not compatible with the wait() and as_completed()
methods in the concurrent.futures package.
(In Python 3.4 or later we may be able to unify the implementations.)
NF©Úloopc óä — |€t j ¦ « | _ n|| _ g | _ | j ¦ « r-t j t j d¦ « ¦ « | _ dS dS )zÛInitialize the future.
The optional event_loop argument allows explicitly setting the event
loop object used by the future. If it's not provided, the future uses
the default event loop.
Nr )
r Ú_get_event_loopÚ_loopÚ
_callbacksÚ get_debugr Ú
extract_stackÚsysÚ _getframeÚ_source_traceback©Úselfr s ú6/opt/alt/python311/lib64/python3.11/asyncio/futures.pyÚ__init__zFuture.__init__H sq € ð ˆ<ÝÔ/Ñ1Ô1ˆDŒJˆJàˆDŒJ؈ŒØŒ:×ÒÑ!Ô!ð "Ý%3Ô%AÝ”
˜aÑ Ô ñ&"ô &"ˆDÔ"Ð"Ð"ð "ð "ó c ó* — t j | ¦ « S ©N)r Ú_future_repr©r s r Ú__repr__zFuture.__repr__X s € ÝÔ(¨Ñ.Ô.Ð.r c ó¢ — | j sd S | j }| j j › d�|| dœ}| j r
| j |d<