⚝
One Hat Cyber Team
⚝
Your IP:
216.73.216.144
Server IP:
157.245.143.252
Server:
Linux www 6.11.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 14 13:19:59 UTC 2024 x86_64
Server Software:
nginx/1.26.0
PHP Version:
8.3.11
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
lib
/
python3.12
/
asyncio
/
__pycache__
/
View File Name :
futures.cpython-312.pyc
CRh08 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 ZdddZ ddlZej( xZZy# e$ r Y yw 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$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.) NFloopc |t j | _ n|| _ g | _ | j j r.t j t j d | _ yy)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 &/usr/lib/python3.12/asyncio/futures.py__init__zFuture.__init__H s[ <..0DJDJ::!%3%A%A a &"D" " c , t j | S N)r _future_reprr s r __repr__zFuture.__repr__X s ((..r c | j sy | j }| j j d|| d}| j r| j |d<