o )ªZhs ã@sždZddlZddlmZddlZddlZddlZddlmZddl Z ddl m Z m Z m Z m Z mZe  d¡ZGdd„deƒZejZejefZd e d efd d „ZGd d„dejƒZeƒZde de d e fdd„ZeƒZd*dd„Zddded dfdd„Zddded dfdd„Z ddd e e e!e ee ej"fd dfd!d"„Z#e j$dd#d$e d#gdfd dfd%d&„ƒZ%e j$ddd$e dgdfd dfd'd&„ƒZ%ddd$e d(d dfd)d&„Z%dS)+a¨Utilities for working with ``Future`` objects. Tornado previously provided its own ``Future`` class, but now uses `asyncio.Future`. This module contains utility functions for working with `asyncio.Future` in a way that is backwards-compatible with Tornado's old ``Future`` implementation. While this module is an important part of Tornado's internal implementation, applications rarely need to interact with it directly. éN)Úfutures)Úapp_log)ÚAnyÚCallableÚOptionalÚTupleÚUnionÚ_Tc@s eZdZdS)ÚReturnValueIgnoredErrorN)Ú__name__Ú __module__Ú __qualname__©rrúI/var/www/html/lang_env/lib/python3.10/site-packages/tornado/concurrent.pyr *sr ÚxÚreturncCs t|tƒS©N)Ú isinstanceÚFUTURES)rrrrÚ is_future4s rc@sheZdZdedefdededdfdd„Zejd kr(dd e d e ddfdd„Z dSdd e ddfdd„Z dS)Ú DummyExecutorÚfn.ÚargsÚkwargsrúfutures.Future[_T]cOsFt ¡}z t|||i|¤ŽƒW|Sty"t|t ¡ƒY|Swr)rÚFutureÚ"future_set_result_unless_cancelledÚ ExceptionÚfuture_set_exc_infoÚsysÚexc_info)ÚselfrrrÚfuturerrrÚsubmit9s þþzDummyExecutor.submit)éé TFÚwaitÚcancel_futuresNcCódSrr)r!r&r'rrrÚshutdownEózDummyExecutor.shutdowncCr(rr)r!r&rrrr)Jr*)TF)T) r r r rr rr#rÚ version_infoÚboolr)rrrrr8s ÿÿÿ þ rrrcsddtdtdtff‡fdd„ }|rˆrtdƒ‚t|ƒdkr#||dƒSt|ƒdkr0td t|ƒƒ‚|S) aEDecorator to run a synchronous method asynchronously on an executor. Returns a future. The executor to be used is determined by the ``executor`` attributes of ``self``. To use a different attribute name, pass a keyword argument to the decorator:: @run_on_executor(executor='_thread_pool') def foo(self): pass This decorator should not be confused with the similarly-named `.IOLoop.run_in_executor`. In general, using ``run_in_executor`` when *calling* a blocking method is recommended instead of using this decorator when *defining* a method. If compatibility with older versions of Tornado is required, consider defining an executor and using ``executor.submit()`` at the call site. .. versionchanged:: 4.2 Added keyword arguments to use alternative attributes. .. versionchanged:: 5.0 Always uses the current IOLoop instead of ``self.io_loop``. .. versionchanged:: 5.1 Returns a `.Future` compatible with ``await`` instead of a `concurrent.futures.Future`. .. deprecated:: 5.1 The ``callback`` argument is deprecated and will be removed in 6.0. The decorator itself is discouraged in new code but will not be removed in 6.0. .. versionchanged:: 6.0 The ``callback`` argument was removed. rr.c s:ˆ dd¡‰t ˆ¡dtdtdtdtf‡‡fdd„ ƒ}|S)NÚexecutorr!rrrcs4tƒ}t|ˆƒjˆ|g|¢Ri|¤Ž}t||ƒ|Sr)rÚgetattrr#Ú chain_future)r!rrZ async_futureZ conc_future©r-rrrÚwrappers  zCrun_on_executor..run_on_executor_decorator..wrapper)ÚgetÚ functoolsÚwrapsrr)rr1©rr0rÚrun_on_executor_decorator|s "z2run_on_executor..run_on_executor_decoratorz*cannot combine positional and keyword argsérzexpected 1 argument, got %d)rrÚ ValueErrorÚlen)rrr6rr5rÚrun_on_executorQs+    r:Úaú Future[_T]ÚbcsFd ‡fdd„ }t|tƒrt||ƒdSddlm}| ¡ ||¡dS) ajChain two futures together so that when one completes, so does the other. The result (success or failure) of ``a`` will be copied to ``b``, unless ``b`` has already been completed or cancelled by the time ``a`` finishes. .. versionchanged:: 5.0 Now accepts both Tornado/asyncio `Future` objects and `concurrent.futures.Future`. r;r<rNcsdˆ ¡rdSt|dƒr| ¡durtˆ| ¡ƒdS| ¡}|dur)ˆ |¡dSˆ | ¡¡dS)Nr )ÚdoneÚhasattrr rÚ exceptionÚ set_exceptionÚ set_resultÚresult)r;Za_exc©r=rrÚcopy¡szchain_future..copyr)ÚIOLoop)r;r<rN)rrÚfuture_add_done_callbackZtornado.iolooprFÚcurrentZ add_future)r;r=rErFrrDrr/”s   r/r"z%Union[futures.Future[_T], Future[_T]]ÚvaluecCs| ¡s | |¡dSdS)zÐSet the given ``value`` as the `Future`'s result, if not cancelled. Avoids ``asyncio.InvalidStateError`` when calling ``set_result()`` on a cancelled `asyncio.Future`. .. versionadded:: 5.0 N)Ú cancelledrB)r"rIrrrr¶s ÿrÚexccCs(| ¡s | |¡dStjd|ddS)a©Set the given ``exc`` as the `Future`'s exception. If the Future is already canceled, logs the exception instead. If this logging is not desired, the caller should explicitly check the state of the Future and call ``Future.set_exception`` instead of this wrapper. Avoids ``asyncio.InvalidStateError`` when calling ``set_exception()`` on a cancelled `asyncio.Future`. .. versionadded:: 6.0 z$Exception after Future was cancelled)r N)rJrArÚerror)r"rKrrrÚ%future_set_exception_unless_cancelledÄsrMr cCs&|ddur tdƒ‚t||dƒdS)aSet the given ``exc_info`` as the `Future`'s exception. Understands both `asyncio.Future` and the extensions in older versions of Tornado to enable better tracebacks on Python 2. .. versionadded:: 5.0 .. versionchanged:: 6.0 If the future is already cancelled, this function is a no-op. (previously ``asyncio.InvalidStateError`` would be raised) r7Nz,future_set_exc_info called with no exception)rrM)r"r rrrrÚs rrÚcallbackcCr(rr©r"rNrrrrGòórGcCr(rrrOrrrrGùrP).NcCs"| ¡r ||ƒdS| |¡dS)aLArrange to call ``callback`` when ``future`` is complete. ``callback`` is invoked with one argument, the ``future``. If ``future`` is already done, ``callback`` is invoked immediately. This may differ from the behavior of ``Future.add_done_callback``, which makes no such guarantee. .. versionadded:: 5.0 N)r>Zadd_done_callbackrOrrrrGs )r;r<r=r<rN)&Ú__doc__ZasyncioZ concurrentrr3rÚtypesZ tornado.logrÚtypingrrrrrÚTypeVarr rr rrr,rZExecutorrZdummy_executorr:ÚobjectZ _NO_RESULTr/rÚ BaseExceptionrMÚtypeÚ TracebackTyperÚoverloadrGrrrrÚs‚    @ "ÿÿ þÿÿ þÿÿþ ûÿ ÿ þÿ ÿ þÿÿþ