U lu fҏ@sXdZddlZddlZddlZddlZddlZddlZddlZddl Z ddl Z ddl Z ddl Z ddl mZddlmZmZmZmZmZddlmZddlmZmZmZddlZddlmZmZmZmZm Z m!Z!m"Z"m#Z#ej$rddlm%Z%m&Z&m'Z'dd l(m)Z)ne*Z)Gd d d e)Z+e!d Z,e!d e+dZ-GdddeZ.Gddde*Z/Gddde*Z0dS)aAn I/O event loop for non-blocking sockets. In Tornado 6.0, `.IOLoop` is a wrapper around the `asyncio` event loop, with a slightly different interface. The `.IOLoop` interface is now provided primarily for backwards compatibility; new code should generally use the `asyncio` event loop interface directly. The `IOLoop.current` class method provides the `IOLoop` instance corresponding to the running `asyncio` event loop. N) isawaitable)Future is_future chain_futurefuture_set_exc_infofuture_add_done_callback)app_log) Configurable TimeoutError import_object)UnionAnyTypeOptionalCallableTypeVarTuple Awaitable)DictListSet)Protocolc@s(eZdZedddZddddZdS) _SelectablereturncCsdSNselfrr2/tmp/pip-unpacked-wheel-bmg6zs32/tornado/ioloop.pyfileno=sz_Selectable.filenoNcCsdSrrrrrrclose@sz_Selectable.close)__name__ __module__ __qualname__intr r!rrrrr<sr_T_S)boundcseZdZdZdZdZdZdZeZ e Z e de ddfd d Zedd d d Zdd ddZedd ddZejedd ddZejedpeeddddZedqeeddddZdd ddZdd ddZedd ddZedd ddZdd d d!Ze eed d"d#Ze eed d$d%Z dredd&d'd(Z!dsedd*d+d,Z"eje#e$e#e#gdfe#dd-d.d/Z%eje&e$e&e#gdfe#dd-d0d/Z%e'e#e(fe$d1e#dd-d2d/Z%e'e#e(fe#dd3d4d5Z)e'e#e(fdd6d7d8Z*dd d9d:Z+dd d;d<Z,dte$ee-e d=d>d?Z.e-d d@dAZ/e'e-e0j1fe$e e e2dBdCdDZ3e-e$e e e2dEdFdGZ4e-e$e e e2dHdIdJZ5e2ddKdLdMZ6e$e e ddNdOdPZ7e$e e ddNdQdRZ8e$e e ddNdSdTZ9dUe$dVgdfddWdXdYZ:ee;jfe dVd[d\d]Z?e;jz.IOLoop.run_sync..run..) Z tornado.genrc Exceptionrrsysexc_inforZ set_resultAssertionError add_future)resultrcZfutra future_cellrrrruns     zIOLoop.run_sync..runcs(ddk stds$dS)Nr)rjcancelr`r)rnrrrtimeout_callback s z)IOLoop.run_sync..timeout_callbackrz$Operation timed out after %s seconds) add_callback add_timeouttimer_remove_timeoutrjZ cancelleddoner rl)rrarbrorqZtimeout_handlerrmrrun_syncs     zIOLoop.run_synccCstS)aReturns the current time according to the `IOLoop`'s clock. The return value is a floating-point number relative to an unspecified time in the past. Historically, the IOLoop could be customized to use e.g. `time.monotonic` instead of `time.time`, but this is not currently supported and so this method is equivalent to `time.time`. )rtrrrrrts z IOLoop.time)deadlinecallbackargsr.rcOs\t|tjr |j||f||St|tjrL|j|||f||Std|dS)aRuns the ``callback`` at the time ``deadline`` from the I/O loop. Returns an opaque handle that may be passed to `remove_timeout` to cancel. ``deadline`` may be a number denoting a time (on the same scale as `IOLoop.time`, normally `time.time`), or a `datetime.timedelta` object for a deadline relative to the current time. Since Tornado 4.0, `call_later` is a more convenient alternative for the relative case since it does not require a timedelta object. Note that it is not safe to call `add_timeout` from other threads. Instead, you must use `add_callback` to transfer control to the `IOLoop`'s thread, and then call `add_timeout` from there. Subclasses of IOLoop must implement either `add_timeout` or `call_at`; the default implementations of each will call the other. `call_at` is usually easier to implement, but subclasses that wish to maintain compatibility with Tornado versions prior to 4.0 must use `add_timeout` instead. .. versionchanged:: 4.0 Now passes through ``*args`` and ``**kwargs`` to the callback. Unsupported deadline %rN) r1numbersRealcall_atdatetime timedeltart total_seconds TypeError)rrxryrzr.rrrrs+s  zIOLoop.add_timeout)delayryrzr.rcOs|j|||f||S)aRuns the ``callback`` after ``delay`` seconds have passed. Returns an opaque handle that may be passed to `remove_timeout` to cancel. Note that unlike the `asyncio` method of the same name, the returned object does not have a ``cancel()`` method. See `add_timeout` for comments on thread-safety and subclassing. .. versionadded:: 4.0 )r~rt)rrryrzr.rrr call_laterTs zIOLoop.call_later)whenryrzr.rcOs|j||f||S)aRuns the ``callback`` at the absolute time designated by ``when``. ``when`` must be a number using the same reference point as `IOLoop.time`. Returns an opaque handle that may be passed to `remove_timeout` to cancel. Note that unlike the `asyncio` method of the same name, the returned object does not have a ``cancel()`` method. See `add_timeout` for comments on thread-safety and subclassing. .. versionadded:: 4.0 )rs)rrryrzr.rrrr~cszIOLoop.call_at)rbrcCs tdS)zCancels a pending timeout. The argument is a handle as returned by `add_timeout`. It is safe to call `remove_timeout` even if the callback has already been run. NrM)rrbrrrruuszIOLoop.remove_timeout)ryrzr.rcOs tdS)aCalls the given callback on the next I/O loop iteration. It is safe to call this method from any thread at any time, except from a signal handler. Note that this is the **only** method in `IOLoop` that makes this thread-safety guarantee; all other interaction with the `IOLoop` must be done from that `IOLoop`'s thread. `add_callback()` may be used to transfer control from other threads to the `IOLoop`'s thread. NrMrryrzr.rrrrr~s zIOLoop.add_callbackcOs tdS)aCalls the given callback on the next I/O loop iteration. Intended to be afe for use from a Python signal handler; should not be used otherwise. .. deprecated:: 6.4 Use ``asyncio.AbstractEventLoop.add_signal_handler`` instead. This method is suspected to have been broken since Tornado 5.0 and will be removed in version 7.0. NrMrrrradd_callback_from_signals zIOLoop.add_callback_from_signalcOs|j|f||dS)zCalls the given callback on the next IOLoop iteration. As of Tornado 6.0, this method is equivalent to `add_callback`. .. versionadded:: 4.0 Nrrrrrrspawn_callbackszIOLoop.spawn_callbackz0Union[Future[_T], concurrent.futures.Future[_T]]z Future[_T])rdryrcsDt|tr |fddn t|s,tt|fdddS)aASchedules a callback on the ``IOLoop`` when the given `.Future` is finished. The callback is invoked with one argument, the `.Future`. This method only accepts `.Future` objects and not other awaitables (unlike most of Tornado where the two are interchangeable). cst|Sr) _run_callback functoolspartialfryrrrrerfz#IOLoop.add_future..cs |SrrrrrrrerfN)r1rZadd_done_callbackrrjr)rrdryrrrrks    zIOLoop.add_future.)executorrarzrcsh|dkr:t|ds4ddlm}tjj|dd|_|j}|j|f|}t| |fddS) zRuns a function in a ``concurrent.futures.Executor``. If ``executor`` is ``None``, the IO loop's default executor will be used. Use `functools.partial` to pass keyword arguments to ``func``. .. versionadded:: 5.0 N _executorr) cpu_count) max_workerscs t|Sr)rrZt_futurerrrerfz(IOLoop.run_in_executor..) hasattrZtornado.processr concurrentfuturesZThreadPoolExecutorrZsubmitrrk)rrrarzrZc_futurerrrrun_in_executors   zIOLoop.run_in_executor)rrcCs ||_dS)zfSets the default executor to use with :meth:`run_in_executor`. .. versionadded:: 5.0 N)r)rrrrrset_default_executorszIOLoop.set_default_executor)ryrcCszR|}|dk rPddlm}z||}Wn|jk r@YnX|||jWn8tjk rhYn$tk rt j d|ddYnXdS)zRuns a callback with error handling. .. versionchanged:: 6.0 CancelledErrors are no longer logged. Nr)genException in callback %rTri) ZtornadorrcZ BadYieldErrorrk_discard_future_resultrCZCancelledErrorrgrerror)rryretrrrrrs zIOLoop._run_callback)rdrcCs |dS)z;Avoid unhandled-exception warnings from spawned coroutines.N)rl)rrdrrrrszIOLoop._discard_future_resultcCst|tr||fS||fSr)r1r%r r]rrrsplit_fds zIOLoop.split_fdcCs<z"t|trt|n|Wntk r6YnXdSr)r1r%osr!OSErrorr]rrrclose_fds    zIOLoop.close_fd)rrcCs|j|dSr)_pending_tasksaddrrrrr_register_task2szIOLoop._register_taskcCs|j|dSr)rdiscardrrrr_unregister_task5szIOLoop._unregister_task)T)T)T)F)N)Jr"r#r$__doc__NONEREADWRITEERRORdictrDsetr classmethodr r7 staticmethodr<r>r@typingoverloadr;boolrr=rLr?rOrPrr rRrTrUr!r%rr[r'r rr\r^r_r`floatrwrtrrobjectrsrr~rurrrrrkrrZExecutorr&rrrrrrrrrr __classcell__rrr9rr)HsQ  ,     L  *        #     r)c@sVeZdZdZdddgZeegdfeddddZde d d d Z de d d d Z dS)_Timeoutz2An IOLoop timeout, a UNIX timestamp and a callbackrxry tdeadlineN)rxryio_looprcCs8t|tjstd|||_||_|t|jf|_dS)Nr{) r1r|r}rrxrynextZ_timeout_counterr)rrxryrrrr__init__?s  z_Timeout.__init__)otherrcCs |j|jkSrrrrrrr__lt__Osz_Timeout.__lt__cCs |j|jkSrrrrrr__le__Rsz_Timeout.__le__) r"r#r$r __slots__rrr)rrrrrrrrr9s   rc@seZdZdZdegeefeej e fe ddddZ dddd Z ddd d Z edd d ZddddZddddZe ddddZdS)PeriodicCallbackaSchedules the given callback to be called periodically. The callback is called every ``callback_time`` milliseconds when ``callback_time`` is a float. Note that the timeout is given in milliseconds, while most other time-related functions in Tornado use seconds. ``callback_time`` may alternatively be given as a `datetime.timedelta` object. If ``jitter`` is specified, each callback time will be randomly selected within a window of ``jitter * callback_time`` milliseconds. Jitter can be used to reduce alignment of events with similar periods. A jitter of 0.1 means allowing a 10% variation in callback time. The window is centered on ``callback_time`` so the total number of calls within a given interval should not be significantly affected by adding jitter. If the callback runs for longer than ``callback_time`` milliseconds, subsequent invocations will be skipped to get back on schedule. `start` must be called after the `PeriodicCallback` is created. .. versionchanged:: 5.0 The ``io_loop`` argument (deprecated since version 4.1) has been removed. .. versionchanged:: 5.1 The ``jitter`` argument is added. .. versionchanged:: 6.2 If the ``callback`` argument is a coroutine, and a callback runs for longer than ``callback_time``, subsequent invocations will be skipped. Previously this was only true for regular functions, not coroutines, which were "fire-and-forget" for `PeriodicCallback`. The ``callback_time`` argument now accepts `datetime.timedelta` objects, in addition to the previous numeric milliseconds. rN)ry callback_timejitterrcCsR||_t|tjr&|tjdd|_n|dkr6td||_||_d|_d|_dS)Nr*)Z millisecondsrz4Periodic callback must have a positive callback_timeF) ryr1rrr ValueErrorr_running_timeout)rryrrrrrr|s zPeriodicCallback.__init__rcCs(t|_d|_|j|_|dS)zStarts the timer.TN)r)r;rrrt _next_timeout_schedule_nextrrrrr_s  zPeriodicCallback.startcCs(d|_|jdk r$|j|jd|_dS)zStops the timer.FN)rrrrurrrrr`s zPeriodicCallback.stopcCs|jS)zfReturns ``True`` if this `.PeriodicCallback` has been started. .. versionadded:: 4.1 )rrrrr is_runningszPeriodicCallback.is_runningcsl|js dSzRz&|}|dk r0t|r0|IdHWn&tk rXtjd|jddYnXW5|XdS)NrTr)rrryrrgrr)rvalrrr_runszPeriodicCallback._runcCs.|jr*||j|j|j|j|_dSr)r _update_nextrrtrsrrrrrrrrszPeriodicCallback._schedule_next) current_timercCsn|jd}|jr*|d|jtd9}|j|kr\|jt||j|d|7_n|j|7_dS)Ng@@r*g?)rrrandomrmathfloor)rrZcallback_time_secrrrrs   zPeriodicCallback._update_next)r)r"r#r$rrrrr rrrrr_r`rrrrrrrrrrVs)    r)1rrCconcurrent.futuresrrrr|rrhrtrrrIinspectrZtornado.concurrentrrrrrZ tornado.logrZ tornado.utilr r r rr r rrrrrr TYPE_CHECKINGrrrZtyping_extensionsrrrr&r'r)rrrrrrs@   ( v