tornado IOLoop API with zmq compatibility
If you have tornado ≥ 3.0, this is a subclass of tornado’s IOLoop, otherwise we ship a minimal subset of tornado in zmq.eventloop.minitornado.
The minimal shipped version of tornado’s IOLoop does not include support for concurrent futures - this will only be available if you have tornado ≥ 3.0.
Schedules the given callback to be called once.
The callback is called once, after callback_time milliseconds.
start must be called after the DelayedCallback is created.
The timeout is calculated from when start is called.
Starts the timer.
Stops the timer.
ZMQ subclass of tornado’s IOLoop
Schedules a callback on the IOLoop when the given .Future is finished.
The callback is invoked with one argument, the .Future.
Clear the global IOLoop instance.
New in version 3.3.
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.
New in version 3.3.
Sets the class to use when the base class is instantiated.
Keyword arguments will be saved and added to the arguments passed to the constructor. This can be used to set global defaults for some parameters.
Returns the currently configured class.
Returns the current thread’s IOLoop.
If an IOLoop is currently running or has been marked as current by make_current, returns that instance. Otherwise returns IOLoop.instance(), i.e. the main thread’s IOLoop.
A common pattern for classes that depend on IOLoops is to use a default argument to enable programs with multiple IOLoops but not require the argument for simpler applications:
class MyClass(object): def __init__(self, io_loop=None): self.io_loop = io_loop or IOLoop.current()
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.
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.
Returns true if the singleton instance has been created.
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.
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. To get the current thread’s IOLoop, use current().
Signal handler to log the stack trace of the current thread.
For use with set_blocking_signal_threshold.
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 explictly before starting the IOLoop, so that code run at startup time can find the right instance.
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.instance().run_sync(main)
Logs a stack trace if the IOLoop is blocked for more than s seconds.
Equivalent to set_blocking_signal_threshold(seconds, self.log_stack)
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.
New in version 3.3.
A poller that can be used in the tornado IOLoop.
This simply wraps a regular zmq.Poller, scaling the timeout by 1000, so that it is in seconds rather than milliseconds.
poll in seconds rather than milliseconds.
Event masks will be IOLoop.READ/WRITE/ERROR
set the tornado IOLoop instance with the pyzmq IOLoop.
After calling this function, tornado’s IOLoop.instance() and pyzmq’s IOLoop.instance() will return the same object.
An assertion error will be raised if tornado’s IOLoop has been initialized prior to calling this function.