calls finish(), so no other output methods can be called after it. Returns a Future with the same semantics as the one returned by finish. Awaiting this Future is optional. Changed in version 5.1: Now returns tornado.httpserver.HTTPRequest. supports_http_1_1() Returns True if this request supports HTTP/1.1 semantics. Deprecated since version 4.0: Applications are less likely to need this information with the introduction AsyncIOLoop is an IOLoop that runs on an asyncio event loop. This class follows the usual Tornado semantics for creating new IOLoops; these loops are not necessarily related to the asyncio default event loop

calls finish(), so no other output methods can be called after it. Returns a Future with the same semantics as the one returned by finish. Awaiting this Future is optional. Changed in version 5.1: Now returns tornado.httpserver.HTTPRequest. supports_http_1_1() Returns True if this request supports HTTP/1.1 semantics. Deprecated since version 4.0: Applications are less likely to need this information with the introduction AsyncIOLoop is an IOLoop that runs on an asyncio event loop. This class follows the usual Tornado semantics for creating new IOLoops; these loops are not necessarily related to the asyncio default event loop

tornado.httpserver.HTTPRequest. supports_http_1_1() Returns True if this request supports HTTP/1.1 semantics. Deprecated since version 4.0: Applications are less likely to need this information with the introduction AsyncIOLoop is an IOLoop that runs on an asyncio event loop. This class follows the usual Tornado semantics for creating new IOLoops; these loops are not necessarily related to the asyncio default event loop exception_handler function will be called in the event of an uncaught exception in this context. The semantics are similar to a try/finally clause, and intended use cases are to log an error, close a socket

calls finish(), so no other output methods can be called after it. Returns a Future with the same semantics as the one returned by finish. Awaiting this Future is optional. Changed in version 5.1: Now returns AsyncIOLoop is an IOLoop that runs on an asyncio event loop. This class follows the usual Tornado semantics for creating new IOLoops; these loops are not necessarily related to the asyncio default event loop removed in Tornado 6.0. The reason for this is that it is not feasible to provide this module’s semantics in the presence of async def native coroutines. ExceptionStackContext is mainly obsolete thanks

tornado.httpserver.HTTPRequest. supports_http_1_1() Returns True if this request supports HTTP/1.1 semantics. Deprecated since version 4.0: Applications are less likely to need this information with the introduction AsyncIOLoop is an IOLoop that runs on an asyncio event loop. This class follows the usual Tornado semantics for creating new IOLoops; these loops are not necessarily related to the asyncio default event loop exception_handler function will be called in the event of an uncaught exception in this context. The semantics are similar to a try/finally clause, and intended use cases are to log an error, close a socket

calls finish(), so no other output methods can be called after it. Returns a Future with the same semantics as the one returned by finish. Awaiting this Future is optional. Changed in version 5.1: Now returns AsyncIOLoop is an IOLoop that runs on an asyncio event loop. This class follows the usual Tornado semantics for creating new IOLoops; these loops are not necessarily related to the asyncio default event loop removed in Tornado 6.0. The reason for this is that it is not feasible to provide this module’s semantics in the presence of async def native coroutines. ExceptionStackContext is mainly obsolete thanks

calls finish(), so no other output methods can be called after it. Returns a Future with the same semantics as the one returned by finish. Awaiting this Future is optional. Changed in version 5.1: Now returns AsyncIOLoop is an IOLoop that runs on an asyncio event loop. This class follows the usual Tornado semantics for creating new IOLoops; these loops are not necessarily related to the asyncio default event loop removed in Tornado 6.0. The reason for this is that it is not feasible to provide this module’s semantics in the presence of async def native coroutines. ExceptionStackContext is mainly obsolete thanks

calls finish(), so no other output methods can be called after it. Returns a Future with the same semantics as the one returned by finish. Awaiting this Future is optional. Changed in version 5.1: Now returns AsyncIOLoop is an IOLoop that runs on an asyncio event loop. This class follows the usual Tornado semantics for creating new IOLoops; these loops are not necessarily related to the asyncio default event loop removed in Tornado 6.0. The reason for this is that it is not feasible to provide this module’s semantics in the presence of async def native coroutines. ExceptionStackContext is mainly obsolete thanks

calls finish(), so no other output methods can be called after it. Returns a Future with the same semantics as the one returned by finish. Awaiting this Future is optional. Changed in version 5.1: Now returns AsyncIOLoop is an IOLoop that runs on an asyncio event loop. This class follows the usual Tornado semantics for creating new IOLoops; these loops are not necessarily related to the asyncio default event loop removed in Tornado 6.0. The reason for this is that it is not feasible to provide this module’s semantics in the presence of async def native coroutines. ExceptionStackContext is mainly obsolete thanks

calls finish(), so no other output methods can be called after it. Returns a Future with the same semantics as the one returned by finish. Awaiting this Future is optional. Changed in version 5.1: Now returns AsyncIOLoop is an IOLoop that runs on an asyncio event loop. This class follows the usual Tornado semantics for creating new IOLoops; these loops are not necessarily related to the asyncio default event loop removed in Tornado 6.0. The reason for this is that it is not feasible to provide this module’s semantics in the presence of async def native coroutines. ExceptionStackContext is mainly obsolete thanks