Current Path: > > opt > alt > python34 > lib64 > python3.4 > > asyncio > > > __pycache__
Operation : Linux premium131.web-hosting.com 4.18.0-553.44.1.lve.el8.x86_64 #1 SMP Thu Mar 13 14:29:12 UTC 2025 x86_64 Software : Apache Server IP : 162.0.232.56 | Your IP: 216.73.216.111 Domains : 1034 Domain(s) Permission : [ 0755 ]
Name | Type | Size | Last Modified | Actions |
---|---|---|---|---|
__init__.cpython-34.pyc | File | 870 bytes | April 17 2024 17:10:10. | |
__init__.cpython-34.pyo | File | 870 bytes | April 17 2024 17:10:10. | |
base_events.cpython-34.pyc | File | 38167 bytes | April 17 2024 17:10:10. | |
base_events.cpython-34.pyo | File | 37835 bytes | April 17 2024 17:10:06. | |
base_subprocess.cpython-34.pyc | File | 9821 bytes | April 17 2024 17:10:10. | |
base_subprocess.cpython-34.pyo | File | 9696 bytes | April 17 2024 17:10:06. | |
compat.cpython-34.pyc | File | 751 bytes | April 17 2024 17:10:10. | |
compat.cpython-34.pyo | File | 751 bytes | April 17 2024 17:10:10. | |
constants.cpython-34.pyc | File | 242 bytes | April 17 2024 17:10:10. | |
constants.cpython-34.pyo | File | 242 bytes | April 17 2024 17:10:10. | |
coroutines.cpython-34.pyc | File | 8702 bytes | April 17 2024 17:10:10. | |
coroutines.cpython-34.pyo | File | 8569 bytes | April 17 2024 17:10:06. | |
events.cpython-34.pyc | File | 24188 bytes | April 17 2024 17:10:10. | |
events.cpython-34.pyo | File | 23979 bytes | April 17 2024 17:10:06. | |
futures.cpython-34.pyc | File | 15660 bytes | April 17 2024 17:10:10. | |
futures.cpython-34.pyo | File | 15386 bytes | April 17 2024 17:10:06. | |
locks.cpython-34.pyc | File | 15697 bytes | April 17 2024 17:10:10. | |
locks.cpython-34.pyo | File | 15697 bytes | April 17 2024 17:10:10. | |
log.cpython-34.pyc | File | 244 bytes | April 17 2024 17:10:10. | |
log.cpython-34.pyo | File | 244 bytes | April 17 2024 17:10:10. | |
proactor_events.cpython-34.pyc | File | 18009 bytes | April 17 2024 17:10:10. | |
proactor_events.cpython-34.pyo | File | 17763 bytes | April 17 2024 17:10:06. | |
protocols.cpython-34.pyc | File | 6091 bytes | April 17 2024 17:10:10. | |
protocols.cpython-34.pyo | File | 6091 bytes | April 17 2024 17:10:10. | |
queues.cpython-34.pyc | File | 8931 bytes | April 17 2024 17:10:10. | |
queues.cpython-34.pyo | File | 8931 bytes | April 17 2024 17:10:10. | |
selector_events.cpython-34.pyc | File | 30998 bytes | April 17 2024 17:10:10. | |
selector_events.cpython-34.pyo | File | 30933 bytes | April 17 2024 17:10:06. | |
sslproto.cpython-34.pyc | File | 21304 bytes | April 17 2024 17:10:10. | |
sslproto.cpython-34.pyo | File | 21053 bytes | April 17 2024 17:10:06. | |
streams.cpython-34.pyc | File | 20845 bytes | April 17 2024 17:10:10. | |
streams.cpython-34.pyo | File | 20488 bytes | April 17 2024 17:10:06. | |
subprocess.cpython-34.pyc | File | 7152 bytes | April 17 2024 17:10:10. | |
subprocess.cpython-34.pyo | File | 7116 bytes | April 17 2024 17:10:06. | |
tasks.cpython-34.pyc | File | 22851 bytes | April 17 2024 17:10:10. | |
tasks.cpython-34.pyo | File | 22647 bytes | April 17 2024 17:10:06. | |
test_utils.cpython-34.pyc | File | 16338 bytes | April 17 2024 17:10:10. | |
test_utils.cpython-34.pyo | File | 15931 bytes | April 17 2024 17:10:06. | |
transports.cpython-34.pyc | File | 12163 bytes | April 17 2024 17:10:10. | |
transports.cpython-34.pyo | File | 12127 bytes | April 17 2024 17:10:06. | |
unix_events.cpython-34.pyc | File | 31378 bytes | April 17 2024 17:10:10. | |
unix_events.cpython-34.pyo | File | 30967 bytes | April 17 2024 17:10:06. | |
windows_events.cpython-34.pyc | File | 23308 bytes | April 17 2024 17:10:10. | |
windows_events.cpython-34.pyo | File | 23308 bytes | April 17 2024 17:10:10. | |
windows_utils.cpython-34.pyc | File | 5943 bytes | April 17 2024 17:10:10. | |
windows_utils.cpython-34.pyo | File | 5841 bytes | April 17 2024 17:10:06. |
� j f�? � @ s? d Z d d d d d g Z d d l Z d d l Z d d l Z d d l Z d d l Z d d l m Z d d l m Z d Z d Z d Z e j j j Z e j j Z e j j Z e j d Z Gd d � d e � Z Gd d � d � Z Gd d � d � Z d d � Z d d � Z d d � Z d d � Z d d d d � Z d S)z.A Future class similar to the one in PEP 3148.�CancelledError�TimeoutError�InvalidStateError�Future�wrap_future� N� )�compat)�eventsZPENDINGZ CANCELLEDZFINISHEDc @ s e Z d Z d Z d S)r z+The operation is not allowed in this state.N)�__name__� __module__�__qualname__�__doc__� r r �4/opt/alt/python34/lib64/python3.4/asyncio/futures.pyr s c @ sL e Z d Z d Z d Z d d � Z d d � Z d d � Z d d � Z d S)�_TracebackLoggera Helper to log a traceback upon destruction if not cleared. This solves a nasty problem with Futures and Tasks that have an exception set: if nobody asks for the exception, the exception is never logged. This violates the Zen of Python: 'Errors should never pass silently. Unless explicitly silenced.' However, we don't want to log the exception as soon as set_exception() is called: if the calling code is written properly, it will get the exception and handle it properly. But we *do* want to log it if result() or exception() was never called -- otherwise developers waste a lot of time wondering why their buggy code fails silently. An earlier attempt added a __del__() method to the Future class itself, but this backfired because the presence of __del__() prevents garbage collection from breaking cycles. A way out of this catch-22 is to avoid having a __del__() method on the Future class itself, but instead to have a reference to a helper object with a __del__() method that logs the traceback, where we ensure that the helper object doesn't participate in cycles, and only the Future has a reference to it. The helper object is added when set_exception() is called. When the Future is collected, and the helper is present, the helper object is also collected, and its __del__() method will log the traceback. When the Future's result() or exception() method is called (and a helper object is present), it removes the helper object, after calling its clear() method to prevent it from logging. One downside is that we do a fair amount of work to extract the traceback from the exception, even when it is never logged. It would seem cheaper to just store the exception object, but that references the traceback, which references stack frames, which may reference the Future, which references the _TracebackLogger, and then the _TracebackLogger would be included in a cycle, which is what we're trying to avoid! As an optimization, we don't immediately format the exception; we only do the work when activate() is called, which call is delayed until after all the Future's callbacks have run. Since usually a Future has at least one callback (typically set by 'yield from') and usually that callback extracts the callback, thereby removing the need to format the exception. PS. I don't claim credit for this solution. I first heard of it in a discussion about closing files when they are collected. �loop�source_traceback�exc�tbc C s. | j | _ | j | _ | | _ d | _ d S)N)�_loopr �_source_tracebackr r r )�self�futurer r r r �__init__U s z_TracebackLogger.__init__c C sC | j } | d k r? d | _ t j | j | | j � | _ n d S)N)r � traceback�format_exception� __class__� __traceback__r )r r r r r �activate[ s z_TracebackLogger.activatec C s d | _ d | _ d S)N)r r )r r r r �clearb s z_TracebackLogger.clearc C s� | j r� d } | j rT d j t j | j � � } | d 7} | d | j � 7} n | d j | j � j � 7} | j j i | d 6� n d S)Nz*Future/Task exception was never retrieved � z0Future/Task created at (most recent call last): z%s �message)r r �joinr �format_list�rstripr �call_exception_handler)r �msg�srcr r r �__del__f s z_TracebackLogger.__del__N)zloopzsource_tracebackzexcztb) r r r r � __slots__r r r r( r r r r r ! s 0r c @ s* e Z d Z d Z e Z d Z d Z d Z d Z d Z d Z d Z d d d d � Z d d � Z d d � Z d d � Z e j r� d d � Z n d d � Z d d � Z d d � Z d d � Z d d � Z d d � Z d d � Z d d � Z d d � Z d! d"