Ë c‡½j8 ã ój — 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( xZZy# e$ r Y yw 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$y)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 j « r.t j t j d« « | _ yy)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 ú(/usr/lib64/python3.12/asyncio/futures.pyÚ__init__zFuture.__init__H s[ € ð ˆ<Ü×.Ñ.Ó0ˆD�JàˆDŒJ؈ŒØ�:‰:×ÑÔ!Ü%3×%AÑ%AÜ— ‘ ˜aÓ ó&"ˆDÕ"ð "ó c ó, — t j | « S ©N)r Ú_future_repr©r s r Ú__repr__zFuture.__repr__X s € Ü×(Ñ(¨Ó.Ð.r c óÜ — | j sy | j }| j j › d�|| dœ}| j r| j |d<