Tornado’s own interfaces (such as tornado.web) directly instead of using WSGI. In general, Tornado code is not thread-safe. The only method in Tornado that is safe to call from other threads is IOLoop.add_callback referencing any Tornado objects. run_in_executor is the recommended way to interact with blocking code. Installation pip install tornado Tornado is listed in PyPI [http://pypi.python.org/pypi/tornado] asyncio — Bridge between asyncio and Tornado Utilities tornado.autoreload — Automatically detect code changes in development tornado.concurrent — Work with Future objects tornado.log — Logging support

Tornado’s own interfaces (such as tornado.web) directly instead of using WSGI. In general, Tornado code is not thread-safe. The only method in Tornado that is safe to call from other threads is IOLoop.add_callback referencing any Tornado objects. run_in_executor is the recommended way to interact with blocking code. 7 Tornado Documentation, Release 5.1.1 8 Chapter 3. Threads and WSGI CHAPTER 4 Installation used to implement other protocols. • A coroutine library (tornado.gen) which allows asynchronous code to be written in a more straightforward way than chaining callbacks. This is similar to the native

— Basic IOStream-based TCP server Coroutines and concurrency tornado.gen — Simplify asynchronous code tornado.concurrent — Work with threads and futures tornado.locks – Synchronization primitives tornado twisted — Bridges between Twisted and Tornado Utilities tornado.autoreload — Automatically detect code changes in development tornado.log — Logging support tornado.options — Command-line parsing tornado Exception handling across asynchronous callbacks tornado.testing — Unit testing support for asynchronous code tornado.util — General-purpose utilities Frequently Asked Questions Release notes What’s new in

Tornado’s own interfaces (such as tornado.web) directly instead of using WSGI. In general, Tornado code is not thread-safe. The only method in Tornado that is safe to call from other threads is IOLoop.add_callback referencing any Tornado objects. run_in_executor is the recommended way to interact with blocking code. 7 Tornado Documentation, Release 6.1 8 Chapter 3. Threads and WSGI CHAPTER 4 asyncio Integration used to implement other protocols. • A coroutine library (tornado.gen) which allows asynchronous code to be written in a more straightforward way than chaining callbacks. This is similar to the native

Tornado’s own interfaces (such as tornado.web) directly instead of using WSGI. In general, Tornado code is not thread-safe. The only method in Tornado that is safe to call from other threads is IOLoop.add_callback referencing any Tornado objects. run_in_executor is the recommended way to interact with blocking code. 7 Tornado Documentation, Release 6.0.4 8 Chapter 3. Threads and WSGI CHAPTER FOUR ASYNCIO INTEGRATION used to implement other protocols. • A coroutine library (tornado.gen) which allows asynchronous code to be written in a more straightforward way than chaining callbacks. This is similar to the native

used to implement other protocols. • A coroutine library (tornado.gen) which allows asynchronous code to be written in a more straightforward way than chaining callbacks. The Tornado web framework and concurrent connections, Tornado uses a single-threaded event loop. This means that all application code should aim to be asynchronous and non-blocking because only one operation can be active at a time performance comparable to asynchronous systems, but they do not actually make things asynchronous). Examples Here is a sample synchronous function: from tornado.httpclient import HTTPClient def synchronous_fetch(url):

Tornado’s own interfaces (such as tornado.web) directly instead of using WSGI. In general, Tornado code is not thread-safe. The only method in Tornado that is safe to call from other threads is IOLoop.add_callback referencing any Tornado objects. run_in_executor is the recommended way to interact with blocking code. asyncio Integration Tornado is integrated with the standard library asyncio [https://docs.python asyncio — Bridge between asyncio and Tornado Utilities tornado.autoreload — Automatically detect code changes in development tornado.concurrent — Work with Future objects tornado.log — Logging support

Tornado’s own interfaces (such as tornado.web) directly instead of using WSGI. In general, Tornado code is not thread-safe. The only method in Tornado that is safe to call from other threads is IOLoop.add_callback referencing any Tornado objects. run_in_executor is the recommended way to interact with blocking code. 7Tornado Documentation, Release 6.5.1 8 Chapter 3. Threads and WSGICHAPTER FOUR ASYNCIO INTEGRATION concurrent connections, Tornado uses a single-threaded event loop. This means that all appli- cation code should aim to be asynchronous and non-blocking because only one operation can be active at a time

Tornado’s own interfaces (such as tornado.web) directly instead of using WSGI. In general, Tornado code is not thread-safe. The only method in Tornado that is safe to call from other threads is IOLoop.add_callback referencing any Tornado objects. run_in_executor is the recommended way to interact with blocking code. 7 Tornado Documentation, Release 6.4 8 Chapter 3. Threads and WSGI CHAPTER FOUR ASYNCIO INTEGRATION concurrent connections, Tornado uses a single-threaded event loop. This means that all appli- cation code should aim to be asynchronous and non-blocking because only one operation can be active at a time

Tornado’s own interfaces (such as tornado.web) directly instead of using WSGI. In general, Tornado code is not thread-safe. The only method in Tornado that is safe to call from other threads is IOLoop.add_callback referencing any Tornado objects. run_in_executor is the recommended way to interact with blocking code. 7 Tornado Documentation, Release 6.4 8 Chapter 3. Threads and WSGI CHAPTER FOUR ASYNCIO INTEGRATION concurrent connections, Tornado uses a single-threaded event loop. This means that all appli- cation code should aim to be asynchronous and non-blocking because only one operation can be active at a time