a ވa@sdZddlmZmZmZmZddlZddlZddlZddl Z ddl Z ddl Z ddl Z ddl Z ddlZddlZddlZddlZddlZddlZddlmZmZddlmZmZddlmZddlmZmZmZz ddl Z Wne!ydZ Yn0z ddl"Z"Wne!yddl#Z"Yn0dd l$m%Z%m&Z&d Z'Gd d d e(Z)Gd ddeZ*Gddde*Z+Gddde,Z-Gddde,Z.dS)aAn I/O event loop for non-blocking sockets. Typical applications will use a single `IOLoop` object, in the `IOLoop.instance` singleton. The `IOLoop.start` method should usually be called at the end of the ``main()`` function. Atypical applications may use more than one `IOLoop`, such as one `IOLoop` per thread, or per `unittest` case. In addition to I/O events, the `IOLoop` can also schedule time-based events. `IOLoop.add_timeout` is a non-blocking alternative to `time.sleep`. )absolute_importdivisionprint_functionwith_statementN)TracebackFuture is_future)app_loggen_log) stack_context) Configurableerrno_from_exceptiontimedelta_to_seconds)set_close_execWakerg @c@s eZdZdS) TimeoutErrorN)__name__ __module__ __qualname__rr?lib/python3.9/site-packages/zmq/eventloop/minitornado/ioloop.pyrCsrc@seZdZdZdZdZdZdZdZdZ dZ d Z d Z eZ eZeeBZeZeZed d Zed dZddZeddZedRddZddZeddZeddZeddZdSdd Z dTd"d#Z!d$d%Z"d&d'Z#d(d)Z$d*d+Z%d,d-Z&d.d/Z'd0d1Z(d2d3Z)d4d5Z*dUd6d7Z+d8d9Z,d:d;Z-dd?Z/d@dAZ0dBdCZ1dDdEZ2dFdGZ3dHdIZ4dJdKZ5dLdMZ6dNdOZ7dPdQZ8dS)VIOLoopaA level-triggered I/O loop. We use ``epoll`` (Linux) or ``kqueue`` (BSD and Mac OS X) if they are available, or else we fall back on select(). If you are implementing a system that needs to handle thousands of simultaneous connections, you should use a system that supports either ``epoll`` or ``kqueue``. Example usage for a simple TCP server: .. testcode:: import errno import functools import tornado.ioloop import socket def connection_ready(sock, fd, events): while True: try: connection, address = sock.accept() except socket.error as e: if e.args[0] not in (errno.EWOULDBLOCK, errno.EAGAIN): raise return connection.setblocking(0) handle_connection(connection, address) if __name__ == '__main__': sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM, 0) sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1) sock.setblocking(0) sock.bind(("", port)) sock.listen(128) io_loop = tornado.ioloop.IOLoop.current() callback = functools.partial(connection_ready, sock) io_loop.add_handler(sock.fileno(), callback, io_loop.READ) io_loop.start() .. testoutput:: :hide: By default, a newly-constructed `IOLoop` becomes the thread's current `IOLoop`, unless there already is a current `IOLoop`. This behavior can be controlled with the ``make_current`` argument to the `IOLoop` constructor: if ``make_current=True``, the new `IOLoop` will always try to become current and it raises an error if there is already a current instance. If ``make_current=False``, the new `IOLoop` will not try to become current. .. versionchanged:: 4.2 Added the ``make_current`` keyword argument to the `IOLoop` constructor. ri i@lrcCsHttdsBtj"ttds$tt_Wdn1s80YtjS)a1Returns a global `IOLoop` instance. Most applications have a single, global `IOLoop` running on the main thread. Use this method to get this instance from another thread. In most other cases, it is better to use `current()` to get the current thread's `IOLoop`. _instanceN)hasattrr_instance_lockrrrrrinstances  &zIOLoop.instancecCs ttdS)z8Returns true if the singleton instance has been created.r)rrrrrr initializedszIOLoop.initializedcCstr J|t_dS)zInstalls this `IOLoop` object as the singleton instance. This is normally not necessary as `instance()` will create an `IOLoop` on demand, but you may want to call `install` to use a custom subclass of `IOLoop`. N)rr rselfrrrinstalls zIOLoop.installcCsttdrt`dS)zKClear the global `IOLoop` instance. .. versionadded:: 4.0 rN)rrrrrrrclear_instances zIOLoop.clear_instanceTcCs&ttjdd}|dur"|r"tS|S)aReturns the current thread's `IOLoop`. If an `IOLoop` is currently running or has been marked as current by `make_current`, returns that instance. If there is no current `IOLoop`, returns `IOLoop.instance()` (i.e. the main thread's `IOLoop`, creating one if necessary) if ``instance`` is true. In general you should use `IOLoop.current` as the default when constructing an asynchronous object, and use `IOLoop.instance` when you mean to communicate to the main thread from a different one. .. versionchanged:: 4.1 Added ``instance`` argument to control the fallback to `IOLoop.instance()`. rN)getattrr_currentr)rcurrentrrrr's zIOLoop.currentcCs |tj_dS)aMakes this the `IOLoop` for the current thread. An `IOLoop` automatically becomes current for its thread when it is started, but it is sometimes useful to call `make_current` explicitly before starting the `IOLoop`, so that code run at startup time can find the right instance. .. versionchanged:: 4.1 An `IOLoop` created while there is no current `IOLoop` will automatically become current. Nrr&rr!rrr make_currents zIOLoop.make_currentcCs dtj_dSNr(rrrr clear_currentszIOLoop.clear_currentcCstSr*)r)clsrrrconfigurable_baseszIOLoop.configurable_basecCs:ddlm}|Sttdr*ddlm}|Sddlm }|S)Nr) ZMQIOLoopZepoll) EPollIOLoopZkqueue) KQueueIOLoop) SelectIOLoop) Zzmq.eventloop.ioloopr.rselectZtornado.platform.epollr/Ztornado.platform.kqueuer0Ztornado.platform.selectr1)r,r.r/r0r1rrrconfigurable_defaults    zIOLoop.configurable_defaultNcCsJ|dur"tjdddurF|n$|rFtjdddur>td|dS)NF)rzcurrent IOLoop already exists)rr'r) RuntimeError)r"r)rrr initializes zIOLoop.initializeFcCs tdS)aCloses the `IOLoop`, freeing any resources used. If ``all_fds`` is true, all file descriptors registered on the IOLoop will be closed (not just the ones created by the `IOLoop` itself). Many applications will only use a single `IOLoop` that runs for the entire lifetime of the process. In that case closing the `IOLoop` is not necessary since everything will be cleaned up when the process exits. `IOLoop.close` is provided mainly for scenarios such as unit tests, which create and destroy a large number of ``IOLoops``. An `IOLoop` must be completely stopped before it can be closed. This means that `IOLoop.stop()` must be called *and* `IOLoop.start()` must be allowed to return before attempting to call `IOLoop.close()`. Therefore the call to `close` will usually appear just after the call to `start` rather than near the call to `stop`. .. versionchanged:: 3.1 If the `IOLoop` implementation supports non-integer objects for "file descriptors", those objects will have their ``close`` method when ``all_fds`` is true. NNotImplementedError)r"all_fdsrrrclosesz IOLoop.closecCs tdS)aRegisters the given handler to receive the given events for ``fd``. The ``fd`` argument may either be an integer file descriptor or a file-like object with a ``fileno()`` method (and optionally a ``close()`` method, which may be called when the `IOLoop` is shut down). The ``events`` argument is a bitwise or of the constants ``IOLoop.READ``, ``IOLoop.WRITE``, and ``IOLoop.ERROR``. When an event occurs, ``handler(fd, events)`` will be run. .. versionchanged:: 4.0 Added the ability to pass file-like objects in addition to raw file descriptors. Nr6)r"fdhandlereventsrrr add_handlerszIOLoop.add_handlercCs tdS)zChanges the events we listen for ``fd``. .. versionchanged:: 4.0 Added the ability to pass file-like objects in addition to raw file descriptors. Nr6)r"r:r<rrrupdate_handler1szIOLoop.update_handlercCs tdS)zStop listening for events on ``fd``. .. versionchanged:: 4.0 Added the ability to pass file-like objects in addition to raw file descriptors. Nr6r"r:rrrremove_handler:szIOLoop.remove_handlercCs tdS)aSends a signal if the `IOLoop` is blocked for more than ``s`` seconds. Pass ``seconds=None`` to disable. Requires Python 2.6 on a unixy platform. The action parameter is a Python signal handler. Read the documentation for the `signal` module for more information. If ``action`` is None, the process will be killed if it is blocked for too long. Nr6r"secondsactionrrrset_blocking_signal_thresholdCs z$IOLoop.set_blocking_signal_thresholdcCs|||jdS)zLogs a stack trace if the `IOLoop` is blocked for more than ``s`` seconds. Equivalent to ``set_blocking_signal_threshold(seconds, self.log_stack)`` N)rD log_stack)r"rBrrrset_blocking_log_thresholdQsz!IOLoop.set_blocking_log_thresholdc Cs td|jdt|dS)z|Signal handler to log the stack trace of the current thread. For use with `set_blocking_signal_threshold`. z#IOLoop blocked for %f seconds in %sN)r Zwarning_blocking_signal_thresholdjoin traceback format_stack)r"signalframerrrrEZszIOLoop.log_stackcCs tdS)zStarts the I/O loop. The loop will run until one of the callbacks calls `stop()`, which will make the loop stop after the current event iteration completes. Nr6r!rrrstartcsz IOLoop.startcCs0ttjtdjtdjgs,tdS)aThe IOLoop catches and logs exceptions, so it's important that log output be visible. However, python's default behavior for non-root loggers (prior to python 3.2) is to print an unhelpful "no handlers could be found" message rather than the actual log entry, so we must explicitly configure logging if we've made it this far without anything. This method should be called from start() in subclasses. tornadoztornado.applicationN)anyloggingZ getLoggerhandlersZ basicConfigr!rrr_setup_loggingks   zIOLoop._setup_loggingcCs tdS)aAStop the I/O loop. If the event loop is not currently running, the next call to `start()` will return immediately. To use asynchronous methods from otherwise-synchronous code (such as unit tests), you can start and stop the event loop like this:: ioloop = IOLoop() async_method(ioloop=ioloop, callback=ioloop.stop) ioloop.start() ``ioloop.start()`` will return after ``async_method`` has run its callback, whether that callback was invoked before or after ``ioloop.start``. Note that even after `stop` has been called, the `IOLoop` is not completely stopped until `IOLoop.start` has also returned. Some work that was scheduled before the call to `stop` may still be run before the `IOLoop` shuts down. Nr6r!rrrstop{sz IOLoop.stopcs|dgfdd}||dur>|j}|durX|dsptd|dS)aStarts the `IOLoop`, runs the given function, and stops the loop. The function must return either a yieldable object or ``None``. If the function returns a yieldable object, the `IOLoop` will run until the yieldable is resolved (and `run_sync()` will return the yieldable's result). If it raises an exception, the `IOLoop` will stop and the exception will be re-raised to the caller. The keyword-only argument ``timeout`` may be used to set a maximum duration for the function. If the timeout expires, a `TimeoutError` is raised. This method is useful in conjunction with `tornado.gen.coroutine` to allow asynchronous calls in a ``main()`` function:: @gen.coroutine def main(): # do stuff... if __name__ == '__main__': IOLoop.current().run_sync(main) .. versionchanged:: 4.3 Returning a non-``None``, non-yieldable value is now an error. Ncsz&}|dur$ddlm}||}Wn.tyTtd<dtYn,0t|rh|d<ntd<d| dfdddS)Nr)convert_yieldedcsSr*)rTfuturer!rrz.IOLoop.run_sync..run..) Z tornado.genrU ExceptionrZ set_exc_infosysexc_inforZ set_result add_future)resultrUfuncZ future_cellr"rrruns      zIOLoop.run_sync..runrz$Operation timed out after %s seconds) add_callback add_timeouttimerTrNremove_timeoutZdonerr^)r"r`timeoutraZtimeout_handlerr_rrun_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. By default, the `IOLoop`'s time function is `time.time`. However, it may be configured to use e.g. `time.monotonic` instead. Calls to `add_timeout` that pass a number instead of a `datetime.timedelta` should use this function to compute the appropriate time, so they can work no matter what time function is chosen. )rdr!rrrrds z IOLoop.timecOsht|tjr&|j||g|Ri|St|tjrX|j|t||g|Ri|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) isinstancenumbersRealcall_atdatetimeZ timedeltardr TypeError)r"deadlinecallbackargskwargsrrrrcs  zIOLoop.add_timeoutcOs"|j|||g|Ri|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 )rlrd)r"Zdelayrprqrrrrr call_laters zIOLoop.call_latercOs|j||g|Ri|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 )rc)r"ZwhenrprqrrrrrrlszIOLoop.call_atcCs 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. Nr6r"rfrrrreszIOLoop.remove_timeoutcOs tdS)a3Calls 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. To add a callback from a signal handler, see `add_callback_from_signal`. Nr6r"rprqrrrrrrb!s zIOLoop.add_callbackcOs tdS)aSCalls the given callback on the next I/O loop iteration. Safe for use from a Python signal handler; should not be used otherwise. Callbacks added with this method will be run without any `.stack_context`, to avoid picking up the context of the function that was interrupted by the signal. Nr6rurrradd_callback_from_signal0s zIOLoop.add_callback_from_signalcOsDt(|j|g|Ri|Wdn1s60YdS)agCalls the given callback on the next IOLoop iteration. Unlike all other callback-related methods on IOLoop, ``spawn_callback`` does not associate the callback with its caller's ``stack_context``, so it is suitable for fire-and-forget callbacks that should not interfere with the caller. .. versionadded:: 4.0 Nr Z NullContextrbrurrrspawn_callback<s zIOLoop.spawn_callbackcs.t|s Jt|fdddS)zSchedules a callback on the ``IOLoop`` when the given `.Future` is finished. The callback is invoked with one argument, the `.Future`. cs |Sr*)rbrVrpr"rrrXSrYz#IOLoop.add_future..N)rr wrapZadd_done_callback)r"rWrprryrr]Is    zIOLoop.add_futurecCstzR|}|durPddlm}z||}Wn|jy>Yn0||ddWntyn||Yn0dS)zMRuns a callback with error handling. For use in subclasses. Nr)gencSs|Sr*)r^)frrrrXjrYz&IOLoop._run_callback..)rOr{rUZ BadYieldErrorr]rZhandle_callback_exception)r"rpZretr{rrr _run_callbackUs  zIOLoop._run_callbackcCstjd|dddS)aUThis method is called whenever a callback run by the `IOLoop` throws an exception. By default simply logs the exception as an error. Subclasses may override this method to customize reporting of exceptions. The exception itself is not passed explicitly, but is available in `sys.exc_info`. zException in callback %rTr\N)r error)r"rprrrr}ns z IOLoop.handle_callback_exceptioncCs.z||fWSty(||fYS0dS)aReturns an (fd, obj) pair from an ``fd`` parameter. We accept both raw file descriptors and file-like objects as input to `add_handler` and related methods. When a file-like object is passed, we must retain the object itself so we can close it correctly when the `IOLoop` shuts down, but the poller interfaces favor file descriptors (they will accept file-like objects and call ``fileno()`` for you, but they always return the descriptor itself). This method is provided for use by `IOLoop` subclasses and should not generally be used by application code. .. versionadded:: 4.0 N)filenoAttributeErrorr?rrrsplit_fdzs zIOLoop.split_fdcCsFz.z |Wnty*t|Yn0Wnty@Yn0dS)akUtility method to close an ``fd``. If ``fd`` is a file-like object, we close it directly; otherwise we use `os.close`. This method is provided for use by `IOLoop` subclasses (in implementations of ``IOLoop.close(all_fds=True)`` and should not generally be used by application code. .. versionadded:: 4.0 N)r9rosOSErrorr?rrrclose_fds    zIOLoop.close_fd)T)N)F)N)9rrr__doc__Z_EPOLLINZ _EPOLLPRIZ _EPOLLOUTZ _EPOLLERRZ _EPOLLHUPZ _EPOLLRDHUPZ _EPOLLONESHOTZ_EPOLLETZNONEREADZWRITEERROR threadingLockrZlocalr& staticmethodrr r#r$r'r)r+ classmethodr-r3r5r9r=r>r@rDrFrErNrSrTrgrdrcrsrlrerbrvrxr]r~r}rrrrrrrGsp8              7"      rcseZdZdZdfdd ZdddZdd Zd d Zd d ZddZ ddZ ddZ ddZ ddZ ddZddZddZZS) PollIOLoopaBase class for IOLoops built around a select-like function. For concrete implementations, see `tornado.platform.epoll.EPollIOLoop` (Linux), `tornado.platform.kqueue.KQueueIOLoop` (BSD and Mac), or `tornado.platform.select.SelectIOLoop` (all platforms). Nc sttjfi||_tjdr6tj|p>tj_i_ i_ g_ t _g_d_d_d_d_d_d_t_t_jfddjdS)NrrFcs jSr*)_wakerZconsume)r:r<r!rrrXrYz'PollIOLoop.initialize..)superrr5_implrrrrd time_func _handlers_events _callbacksrr_callback_lock _timeouts_cancellations_running_stopped_closing _thread_identrH itertoolscount_timeout_counterrrr=r)r"implrrr __class__r!rr5s,      zPollIOLoop.initializeFcCs|jd|_Wdn1s"0Y||j|r^|jD]\}}||qJ|j|j d|_ d|_ dS)NT) rrr@rrrvaluesrr9rrr)r"r8r:r;rrrr9s$   zPollIOLoop.closecCs:||\}}|t|f|j|<|j|||jBdSr*)rr rzrrregisterr)r"r:r;r<objrrrr=szPollIOLoop.add_handlercCs&||\}}|j|||jBdSr*)rrZmodifyr)r"r:r<rrrrr>szPollIOLoop.update_handlercCs`||\}}|j|d|j|dz|j|Wn tyZtjdddYn0dS)NzError deleting fd from IOLoopTr) rrpoprrZ unregisterrZr debug)r"r:rrrrr@s zPollIOLoop.remove_handlercCsFttdstddS||_|durBttj|dur:|ntjdS)N setitimerzPset_blocking_signal_threshold requires a signal module with the setitimer method)rrLr rrHSIGALRMSIG_DFLrArrrrDs  z(PollIOLoop.set_blocking_signal_thresholdc Cs|jrtd||jr&d|_dSttjdd}|tj_t |_ d|_d}t t drt jdkrz*t |j}|dkrt |d}Wntyd}Yn0z|j|j}g|_Wdn1s0Yg}|jr|}|jrR|jdjdur&t|j|jd 8_q|jdj|krR|t|jqqRq|jd kr|jt|jd ?krd|_d d |jD|_t|j|D]}||q|D]}|jdur||jqd}}}}|jrd }n2|jr|jdj|}t dt!|t"}nt"}|js.q|j#durJt $t j%ddz|j&'|} WnFt(y} z,t)| t*j+krWYd} ~ qnWYd} ~ n d} ~ 00|j#durt $t j%|j#d|j,-| |j,rv|j,.\} } z|j/| \} }|| | Wnrt0t1fyL} z0t)| t*j2kr&n|3|j/4| WYd} ~ n.d} ~ 0t(yp|3|j/4| Yn0qd} }qWd|_|j#durt $t j%dd|tj_|durt |n@d|_|j#durt $t j%dd|tj_|durt |0dS)NzIOLoop is already runningFrT set_wakeup_fdposixrricSsg|]}|jdur|qSr*)rp).0xrrr 9s z$PollIOLoop.start..g)5rr4rSrr%rr&rthread get_identrrrLrnamerrZ write_fileno ValueErrorrrrrdrpheapqheappoprroappendlenheapifyr~maxmin _POLL_TIMEOUTrHr ITIMER_REALrZpollrZr errnoZEINTRrupdatepopitemrrIOErrorZEPIPEr}get)r"Z old_currentZ old_wakeup_fdZ callbacksZ due_timeoutsZnowrprfZ poll_timeoutZ event_pairser:r<Zfd_objZ handler_funcrrrrNs    $       &      zPollIOLoop.startcCsd|_d|_|jdS)NFT)rrrwaker!rrrrTszPollIOLoop.stopcCs|Sr*)rr!rrrrdszPollIOLoop.timecOs8t|tjt|g|Ri||}t|j||Sr*)_Timeout functoolspartialr rzrheappushr)r"rorprqrrrfrrrrlszPollIOLoop.call_atcCsd|_|jd7_dS)Nr)rprrtrrrreszPollIOLoop.remove_timeoutcOst|jkr|jb|jr,WddS|j }|jtjt |g|Ri||rh|j Wdq1s|0Yn0|jrdS|jtjt |g|Ri|dSr*) rrrrrrrrrr rzrr)r"rprqrrZ list_emptyrrrrbs. * zPollIOLoop.add_callbackcOsDt(|j|g|Ri|Wdn1s60YdSr*rwrurrrrvs z#PollIOLoop.add_callback_from_signal)N)F)rrrrr5r9r=r>r@rDrNrTrdrlrerbrv __classcell__rrrrrs     rc@s0eZdZdZgdZddZddZddZd S) rz2An IOLoop timeout, a UNIX timestamp and a callback)rorp tiebreakercCs4t|tjstd|||_||_t|j|_dS)Nrh) rirjrkrnrorpnextrr)r"rorpio_looprrr__init__s   z_Timeout.__init__cCs|j|jf|j|jfkSr*rorr"otherrrr__lt__s  z_Timeout.__lt__cCs|j|jf|j|jfkSr*rrrrr__le__s  z_Timeout.__le__N)rrrr __slots__rrrrrrrrs  rc@sBeZdZdZdddZddZddZd d Zd d Zd dZ dS)PeriodicCallbackaSchedules the given callback to be called periodically. The callback is called every ``callback_time`` milliseconds. Note that the timeout is given in milliseconds, while most other time-related functions in Tornado use seconds. 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:: 4.1 The ``io_loop`` argument is deprecated. NcCs:||_|dkrtd||_|p&t|_d|_d|_dS)Nrz4Periodic callback must have a positive callback_timeF)rpr callback_timerr'rr_timeout)r"rprrrrrrszPeriodicCallback.__init__cCsd|_|j|_|dS)zStarts the timer.TN)rrrd _next_timeout_schedule_nextr!rrrrNs zPeriodicCallback.startcCs(d|_|jdur$|j|jd|_dS)zStops the timer.FN)rrrrer!rrrrTs zPeriodicCallback.stopcCs|jS)zaReturn True if this `.PeriodicCallback` has been started. .. versionadded:: 4.1 )rr!rrr is_runningszPeriodicCallback.is_runningcCs\|js dSzBz|WW|Sty@|j|jYn0W|n |0dSr*)rrprrZrr}r!rrr_runs  zPeriodicCallback._runcCsb|jr^|j}|j|krJ|jd}|jt||j|d|7_|j|j|j|_ dS)Ng@@r) rrrdrrmathZfloorrcrr)r"Z current_timeZcallback_time_secrrrrs    &zPeriodicCallback._schedule_next)N) rrrrrrNrTrrrrrrrrs  r)/rZ __future__rrrrrmrrrrrQrjrr2r[rrdrJrZ concurrentrrlogr r rGr utilr r rrL ImportErrorr_threadZ platform.autorrrrZrrrobjectrrrrrrsP      a&