python (3.11.7)
    e7                     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 ZdddZ	 ddlZej        xZZdS # e$ r Y dS w xY w)z.A Future class similar to the one in PEP 3148.)Futurewrap_futureisfuture    N)GenericAlias   )base_futures)events)
exceptions)format_helpersc                       e Zd ZdZeZdZdZdZdZ	dZ
dZdZdZ
dddZd Zd Z ee          Zed             Zej        d	             Zd
 Zd ZddZd
 Zd Zd Zd Zd ZdddZd 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.)
    NFloopc                    |t          j                    | _        n|| _        g | _        | j                                        r-t          j        t          j        d                    | _	        dS dS )zInitialize 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_stacksys	_getframe_source_tracebackselfr   s     C/BuggyBox/python/3.11.7/bootstrap/lib/python3.11/asyncio/futures.py__init__zFuture.__init__H   sq     </11DJJDJ:!! 	"%3%A
a  &"