Current File : //proc/227033/task/227033/root/usr/lib64/python2.7/site-packages/tornado/ioloop.pyo
�
��L]c @� s d Z d d l m Z m Z m Z m Z d d l Z d d l Z d d l Z d d l Z d d l
Z
d d l Z d d l Z d d l
Z
d d l 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 m Z d d l m Z m Z d d l m Z d d l m Z m Z m Z y d d l Z Wn e! k
rQe" Z n Xy d d l# Z# Wn e! k
r�d d l$ Z# n Xd d l% m& Z& m' Z' d Z( d
e) f d � � YZ* d e f d
� � YZ+ d e+ f d � � YZ, d e- f d � � YZ. d e- f d � � YZ/ d S( s� An 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`.
i ( t absolute_importt divisiont print_functiont with_statementN( t TracebackFuturet is_future( t app_logt gen_log( t
stack_context( t Configurablet errno_from_exceptiont timedelta_to_seconds( t set_close_exect Wakerg �@t TimeoutErrorc B� s e Z RS( ( t __name__t
__module__( ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR B s t IOLoopc B� s� e Z d Z d Z d Z d Z d Z d Z d Z d, Z d- Z
d Z e Z e Z
e e BZ e j � Z e j � Z e d
� � Z e d � � Z d � Z e d
� � Z e e d � � Z d � Z e d � � Z e d � � Z e d � � Z d. d � Z! e" d � Z# d � Z$ d � Z% d � Z& d � Z' d � Z( d � Z) d � Z* d � Z+ d � Z, d. d � Z- d � Z. d � Z/ d! � Z0 d" � Z1 d# � Z2 d$ � Z3 d% � Z4 d& � Z5 d' � Z6 d( � Z7 d) � Z8 d* � Z9 d+ � Z: RS(/ s� A 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.
i i i i i i i i i c C� sG t t d � s@ t j �# t t d � s7 t � t _ n Wd QXn t j S( s1 Returns 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`.
t _instanceN( t hasattrR t _instance_lockR ( ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt instance� s
c C� s
t t d � S( s8 Returns true if the singleton instance has been created.R ( R R ( ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt initialized� s c C� s
| t _ d S( s� Installs 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( R R ( t self( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt install� s c C� s t t d � r t ` n d S( sK Clear the global `IOLoop` instance.
.. versionadded:: 4.0
R N( R R R ( ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt clear_instance� s c C� s5 t t j d d � } | d k r1 | r1 t j � S| S( s� Returns 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()`.
R N( t getattrR t _currentt NoneR ( R t current( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR � s
c C� s | t j _ d S( s� Makes 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.
N( R R R ( R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt make_current� s
c C� s d t j _ d S( N( R R R R ( ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt
clear_current� s c C� s t S( N( R ( t cls( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt configurable_base� s c C� sZ t t d � r# d d l m } | St t d � rF d d l m } | Sd d l m } | S( Nt epolli ( t EPollIOLoopt kqueue( t KQueueIOLoop( t SelectIOLoop( R t selectt tornado.platform.epollR# t tornado.platform.kqueueR% t tornado.platform.selectR& ( R R# R% R& ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt configurable_default� s c C� sr | d k r4 t j d t � d k rn | j � qn n: | rn t j d t � d k ra t d � � n | j � n d S( NR s current IOLoop already exists( R R R t FalseR t RuntimeError( R R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt
initialize� s c C� s
t � � d S( s� Closes 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.
N( t NotImplementedError( R t all_fds( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt close� s c C� s
t � � d S( s� Registers 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.
N( R/ ( R t fdt handlert events( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt add_handler s c C� s
t � � d S( s� Changes the events we listen for ``fd``.
.. versionchanged:: 4.0
Added the ability to pass file-like objects in addition to
raw file descriptors.
N( R/ ( R R2 R4 ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt update_handler- s c C� s
t � � d S( s� Stop listening for events on ``fd``.
.. versionchanged:: 4.0
Added the ability to pass file-like objects in addition to
raw file descriptors.
N( R/ ( R R2 ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt remove_handler6 s c C� s
t � � d S( s� Sends 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.
N( R/ ( R t secondst action( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt set_blocking_signal_threshold? s c C� s | j | | j � d S( s� Logs a stack trace if the `IOLoop` is blocked for more than
``s`` seconds.
Equivalent to ``set_blocking_signal_threshold(seconds,
self.log_stack)``
N( R: t log_stack( R R8 ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt set_blocking_log_thresholdM s c C� s, t j d | j d j t j | � � � d S( s| Signal handler to log the stack trace of the current thread.
For use with `set_blocking_signal_threshold`.
s# IOLoop blocked for %f seconds in
%st N( R t warningt _blocking_signal_thresholdt joint tracebackt format_stack( R t signalt frame( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR; V s c C� s
t � � d S( s� Starts 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.
N( R/ ( R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt start_ s c C� sG t t j � j t j d � j t j d � j g � sC t j � n d S( s� The 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.
t tornados tornado.applicationN( t anyt loggingt getLoggert handlerst basicConfig( R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt _setup_loggingg s c C� s
t � � d S( sA Stop 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.
N( R/ ( R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt stopw s c � s� d g � � � � f d � } � j | � | d k rY � j � j � | � j � } n � j � | d k r � j | � n � d j � s� t d | � � n � d j � S( s
Starts the `IOLoop`, runs the given function, and stops the loop.
If the function returns a `.Future`, the `IOLoop` will run
until the future is resolved. 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)
c � s� y
� � } Wn5 t k
rD t � � d <� d j t j � � n8 Xt | � r^ | � d <n t � � d <� d j | � � j � d � f d � � d S( Ni c � s
� j � S( N( RM ( t future( R ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt <lambda>� s ( t ExceptionR t set_exc_infot syst exc_infoR t
set_resultt
add_future( t result( t funct future_cellR ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt run� s
i s$ Operation timed out after %s secondsN(
R t add_callbackt add_timeoutt timeRM RE t remove_timeoutt doneR RV ( R RW t timeoutRY t timeout_handle( ( RW RX R s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt run_sync� s
"
c C� s
t j � S( s Returns 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.
( R\ ( R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR\ � s
c O� st t | t j � r( | j | | | | � St | t j � r` | j | j � t | � | | | � St d | � � d S( s� Runs 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.
s Unsupported deadline %rN( t
isinstancet numberst Realt call_att datetimet timedeltaR\ R t TypeError( R t deadlinet callbackt argst kwargs( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR[ � s
c O� s | j | j � | | | | � S( s� Runs 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
( Re R\ ( R t delayRj Rk Rl ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt
call_later� s c O� s | j | | | | � S( s� Runs 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
( R[ ( R t whenRj Rk Rl ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRe � s c C� s
t � � d S( s� Cancels 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.
N( R/ ( R R_ ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR] s c O� s
t � � d S( s3 Calls 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`.
N( R/ ( R Rj Rk Rl ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRZ s
c O� s
t � � d S( sS Calls 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.
N( R/ ( R Rj Rk Rl ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt add_callback_from_signal$ s
c O� s* t j � � | j | | | � Wd QXd S( sg Calls 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
N( R t NullContextRZ ( R Rj Rk Rl ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt spawn_callback0 s
c � s, t j � � � | j � � f d � � d S( s� Schedules a callback on the ``IOLoop`` when the given
`.Future` is finished.
The callback is invoked with one argument, the
`.Future`.
c � s � j � | � S( N( RZ ( RN ( Rj R ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRO G s N( R t wrapt add_done_callback( R RN Rj ( ( Rj R s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRU = s c C� s` y; | � } | d k r: t | � r: | j | d � � n Wn t k
r[ | j | � n Xd S( sM Runs a callback with error handling.
For use in subclasses.
c S� s
| j � S( N( RV ( t f( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRO U s N( R R RU RP t handle_callback_exception( R Rj t ret( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt
_run_callbackI s
c C� s t j d | d t �d S( sU This 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`.
s Exception in callback %rRS N( R t errort True( R Rj ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRv Y s
c C� s3 y | j � | f SWn t k
r. | | f SXd S( s� Returns 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( t filenot AttributeError( R R2 ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt split_fde s
c C� sK y3 y | j � Wn t k
r1 t j | � n XWn t k
rF n Xd S( sk Utility 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( R1 R| t ost OSError( R R2 ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt close_fdz s
i @I � N(; R R t __doc__t _EPOLLINt _EPOLLPRIt _EPOLLOUTt _EPOLLERRt _EPOLLHUPt _EPOLLRDHUPt
_EPOLLONESHOTt _EPOLLETt NONEt READt WRITEt ERRORt threadingt LockR t localR t staticmethodR R R R Rz R R R t classmethodR! R+ R R. R, R1 R5 R6 R7 R: R< R; RE RL RM Ra R\ R[ Rn Re R] RZ Rp Rr RU Rx Rv R} R� ( ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR F sd 7
/ "
t
PollIOLoopc B� s� e Z d Z d d � Z e d � Z d � Z d � Z d � Z d � Z
d � Z d � Z d � Z
d
� Z d � Z d � Z d
� Z RS( s Base 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).
c � s t t � � j | � | � _ t � j d � rG t � j j � � n | pS t j � _ i � _ i � _
g � _ t j
� � _ g � _ d � _ t � _ t � _ t � _ d � _ d � _ t j � � _ t � � _ � j � j j � � f d � � j � d S( NR{ i c � s
� j j � S( N( t _wakert consume( R2 R4 ( R ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRO � s ( t superR� R. t _implR R R{ R\ t time_funct _handlerst _eventst
_callbacksR� R� t _callback_lockt _timeoutst _cancellationsR, t _runningt _stoppedt _closingR t
_thread_identR? t itertoolst countt _timeout_counterR
R� R5 R� ( R t implR� Rl ( ( R s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR. � s* c C� s� | j � t | _ Wd QX| j | j j � � | re x- | j j � D] \ } } | j | � qE Wn | j j � | j
j � d | _ d | _
d S( N( R� Rz R� R7 R� R{ R� t valuesR� R1 R� R R� R� ( R R0 R2 R3 ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR1 � s
c C� sO | j | � \ } } | t j | � f | j | <| j j | | | j B� d S( N( R} R Rs R� R� t registerR� ( R R2 R3 R4 t obj( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR5 � s c C� s3 | j | � \ } } | j j | | | j B� d S( N( R} R� t modifyR� ( R R2 R4 R� ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR6 � s c C� sz | j | � \ } } | j j | d � | j j | d � y | j j | � Wn$ t k
ru t j d d t
�n Xd S( Ns Error deleting fd from IOLoopRS ( R} R� t popR R� R� t
unregisterRP R t debugRz ( R R2 R� ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR7 � s
c C� sd t t d � s t j d � d S| | _ | d k r` t j t j | d k rS | n t j � n d S( Nt setitimersP set_blocking_signal_threshold requires a signal module with the setitimer method( R RC R Ry R? R t SIGALRMt SIG_DFL( R R8 R9 ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR: � s
c C� s� | j r t d � � n | j � | j r8 t | _ d St t j d d � } | t j _ t
j � | _ t
| _ d } t t d � r� t j d k r� y> t j | j j � � } | d k r� t j | � d } n Wq� t k
r� d } q� Xn z}xvt
rk| j � | j } g | _ Wd QXg } | j r,| j � } xx | j r�| j d j d k r}t j | j � | j d 8_ q<| j d j | k r�| j t j | j � � q<Pq<W| j d k r,| j t | j � d ?k r,d | _ g | j D] } | j d k r�| ^ q�| _ t j! | j � q,n x | D] } | j" | � q3Wx0 | D]( } | j d k rQ| j" | j � qQqQWd } } } } | j r�d } nD | j r�| j d j | j � } t# d t$ | t% � � } n t% } | j s�Pn | j& d k rt j' t j( d d � n y | j) j* | � }
Wn1 t+ k
rc} t, | � t- j. k r]q� qd� n X| j& d k r�t j' t j( | j& d � n | j/ j0 |
� x� | j/ r]| j/ j1 � \ } }
y$ | j2 | \ } } | | |
� Wq�t3 t4 f k
r0} t, | � t- j5 k rqZ| j6 | j2 j7 | � � q�t+ k
rY| j6 | j2 j7 | � � q�Xq�Wd } } q� WWd t | _ | j& d k r�t j' t j( d d � n | t j _ | d k r�t j | � n Xd S(
Ns IOLoop is already runningR t
set_wakeup_fdt posixi����i i i g (8 R� R- RL R� R, R R R R R t threadt get_identR� Rz R RC R~ t nameR� R� t write_filenot
ValueErrorR� R� R� R\ Rj t heapqt heappopR� Ri t appendt lent heapifyRx t maxt mint
_POLL_TIMEOUTR? R� t ITIMER_REALR� t pollRP R
t errnot EINTRR� t updatet popitemR� R t IOErrort EPIPERv t get( R t old_currentt
old_wakeup_fdt callbackst due_timeoutst nowt xRj R_ t poll_timeoutt event_pairst eR2 R4 t fd_objt handler_func( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRE � s�
! c C� s# t | _ t | _ | j j � d S( N( R, R� Rz R� R� t wake( R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRM u s c C� s
| j � S( N( R� ( R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR\ z s c O� sA t | t j t j | � | | � | � } t j | j | � | S( N( t _Timeoutt functoolst partialR Rs R� t heappushR� ( R Ri Rj Rk Rl R_ ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRe } s c C� s d | _ | j d 7_ d S( Ni ( R Rj R� ( R R_ ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR] � s c O� s� | j �z | j r" t d � � n | j } | j j t j t j | � | | � � | r t j
� | j k r | j j
� n Wd QXd S( Ns IOLoop is closing( R� R� R- R� R� R� R� R Rs R� R� R� R� R� ( R Rj Rk Rl t
list_empty( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRZ � s
c O� sj t j � �X t j � | j k r8 | j | | | � n( | j j t j t j
| � | | � � Wd QXd S( N( R Rq R� R� R� RZ R� R� R� R� Rs ( R Rj Rk Rl ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRp � s
N( R R R� R R. R, R1 R5 R6 R7 R: RE RM R\ Re R] RZ Rp ( ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR� � s
� R� c B� s8 e Z d Z d d d g Z d � Z d � Z d � Z RS( s2 An IOLoop timeout, a UNIX timestamp and a callbackRi Rj t
tiebreakerc C� sM t | t j � s% t d | � � n | | _ | | _ t | j � | _ d S( Ns Unsupported deadline %r( Rb Rc Rd Rh Ri Rj t nextR� R� ( R Ri Rj t io_loop( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt __init__� s
c C� s" | j | j f | j | j f k S( N( Ri R� ( R t other( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt __lt__� s c C� s" | j | j f | j | j f k S( N( Ri R� ( R R� ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt __le__� s ( R R R� t __slots__R� R� R� ( ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR� � s
t PeriodicCallbackc B� sG e Z d Z d d � Z d � Z d � Z d � Z d � Z d � Z RS( s Schedules 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.
c C� sX | | _ | d k r$ t d � � n | | _ | p< t j � | _ t | _ d | _ d S( Ni s4 Periodic callback must have a positive callback_time(
Rj R� t
callback_timeR R R� R, R� R t _timeout( R Rj R� R� ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR� � s c C� s) t | _ | j j � | _ | j � d S( s Starts the timer.N( Rz R� R� R\ t
_next_timeoutt _schedule_next( R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRE � s c C� s; t | _ | j d k r7 | j j | j � d | _ n d S( s Stops the timer.N( R, R� R� R R� R] ( R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyRM � s c C� s | j S( sa Return True if this `.PeriodicCallback` has been started.
.. versionadded:: 4.1
( R� ( R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt
is_running� s c C� sX | j s
d Sz9 y | j � SWn$ t k
rD | j j | j � n XWd | j � Xd S( N( R� Rj RP R� Rv R� ( R ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt _run� s
c C� s� | j r� | j j � } | j | k rb | j d } | j t j | | j | � d | 7_ n | j j | j | j � | _ n d S( Ng @�@i (
R� R� R\ R� R� t matht floorR[ R� R� ( R t current_timet callback_time_sec( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR� s
.N(
R R R� R R� RE RM R� R� R� ( ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyR� � s
(0 R� t
__future__R R R R Rf R� R� R� R� RH Rc R~ R' RR R� R\ RA R� t tornado.concurrentR R t tornado.logR R RF R t tornado.utilR R
R RC t ImportErrorR R� t _threadt tornado.platform.autoR R
R� RP R R R� t objectR� R� ( ( ( s4 /usr/lib64/python2.7/site-packages/tornado/ioloop.pyt <module> sJ "
� � K� #
Mini Shell