o i@sdZddlZddlmZmZmZzddlmZWney'ddlmZYnwddl m Z ddZ d d Z d d Z Gd ddeZdddddZdS)u This implementation is mostly copied from asyncio.tasks (Python 3.8) while making the necessary changes. :copyright: 2021 Nándor Mátravölgyi :license: Apache2, see LICENSE for more details. N)CancelledError ensure_future TimeoutError)get_running_loop)get_event_loop)partialcGs|s |ddSdSN)done set_result)waiterargsr B/home/ubuntu/.local/lib/python3.10/site-packages/wait_for2/impl.py_release_waitersrc CsT|r%z|||Wnty$}z|d||dWYd}~nd}~wwt||)Nzwait_for2 race_handler failed)message exceptionfuture) Exceptioncall_exception_handlerCancelledWithResultError)loopfut fut_result res_exception race_handlerer r r(_handle_cancelling_with_inner_completions rc s|s6|}tt|}|||zz|IdHWn ty(d}YnwW||n ||w|z |IdH}|sE|WSWn-tyZ}z|rR|t|d}~wtys}z|se||}d}WYd}~nd}~wwd}t |||||dS)a The builtin implementation of _cancel_and_wait is made in a way to ensure cancellation of it will always be possible, at the cost of ensuring that the wrapped future shall terminate inside it. The documentation says that - "If a timeout occurs, it cancels the task and raises asyncio.TimeoutError." - "The function will wait until the future is actually cancelled" , but their combination will result in undocumented behaviour: If a timeout occurs and the inner future is cancelled, then cancelling the waiter will instantly cancel it and the inner future may still be running, which does not fulfill the second promise. This implementation will prioritize cancellation or the result of the inner future dynamically as it makes sense. NTF) create_futurerradd_done_callbackcancelrremove_done_callbackrrr) rr cancellingrr cbrexcrr r r_cancel_and_wait2sB    r$cs4eZdZfddZeddZeddZZS)rcstt|||dSr)superr__init__)selfresultr# __class__r rr&Qsz!CancelledWithResultError.__init__cC |jdS)Nrr r'r r rr(T zCancelledWithResultError.resultcCr+)Nr,r-r r r is_exceptionXr.z%CancelledWithResultError.is_exception)__name__ __module__ __qualname__r&propertyr(r0 __classcell__r r r)rrPs   r)rrc s|dur t}n tjdkrtd|dur|IdHS|dkr7t||d}|r-|St||d|IdHS|}| |t |}t t |}t||d}| |ziz|IdHWn@t y|rz|}Wnt ysw|dur|}d}nd}t|||||||t||d|IdHYnw|r|W|S||t||d|IdHW|S|w)aS Alternate implementation of asyncio.wait_for() based on the version from Python 3.8. It handles simultaneous cancellation of wait and completion of future differently and consistently across python versions 3.6+. Builtin asyncio.wait_for() behaviours: Python 3.6, 3.7 and PyPy3: Cancellation of wait_for could lose the completed future's result. Python 3.8+: Cancellation of wait_for could lose the cancellation request. Whenever waiting for a future's result the user expects to either have the future completed or cancelled. Unfortunately due to technical details there is a chance that both will happen simultaneously. The builtin version of asyncio.wait_for() shipped with Python either handles one or the other only. If losing the future's result or ignoring the cancellation is critical to the application it may not be suitable for use. Using this implementation, in case both conditions occur at the same time a subclassed CancelledError will be raised which also contains the result of the future. The caller code must catch this exception and handle the result if it is important. Otherwise it can be used the same way as the builtin wait_for. If the caller prefers to handle the race-condition with a callback, the `race_handler` argument may be provided. It will be called with the result of the future when the waiter task is being cancelled. Even if this is provided, the special error will be raised in the place of a normal CancelledError. Additionally, this implementation will inherit the behaviour of the inner future when it comes to ignoring cancellation. The builtin version prefers to always be cancellable, even if that means the wrapped future may not be terminated with it. (behaviour of builtin _cancel_and_wait) This behaviour is also improved in timeout-cancel edge cases, where the builtin would not wait for the termination of the inner future if the waiter was cancelled after timeout handling had already started. This is more consistent as the inner future must always be stopped for it to return. NOTE: CancelledWithResultError is limited to the coroutine wait_for is invoked from! If this wait_for is wrapped in tasks those will not propagate the special exception, but raise their own CancelledError instances. N) z1loop parameter has been dropped since Python 3.10r)rFT)rsys version_info RuntimeErrorrr r(r$r call_laterrrrrrrr r) rtimeoutrrr timeout_handler"rrr r rwait_for]sR#            r>)__doc__r8asynciorrrr ImportErrorr functoolsrrrr$rr>r r r rs   1