somewhere to go. • Decorated coroutines have additional integration with the concurrent.futures package, allowing the re- sult of executor.submit to be yielded directly. For native coroutines, use IOLoop singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary of Expressions can be any Python expression, including function calls. Template code is executed in a names- pace that includes the following objects and functions (Note that this list applies to templates

somewhere to go. • Decorated coroutines: – have additional integration with the concurrent.futures package, allowing the result of executor.submit to be yielded directly. For native coroutines, use IOLoop Documentation, Release 6.1 Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary of Expressions can be any Python expression, including function calls. Template code is executed in a names- pace that includes the following objects and functions. (Note that this list applies to templates

futures [https://docs.python.org/3.6/library/concurrent.futures.html#module-concurrent.futures] package, allowing the result of executor.submit to be yielded directly. For native coroutines, use IOLoop singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary of RequestHandler, which load templates automatically based on the template_path Application setting. Variable names beginning with _tt_ are reserved by the template system and should not be used by application code

somewhere to go. • Decorated coroutines: – have additional integration with the concurrent.futures package, allowing the result of executor.submit to be yielded directly. For native coroutines, use IOLoop singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary of Expressions can be any Python expression, including function calls. Template code is executed in a names- pace that includes the following objects and functions. (Note that this list applies to templates

somewhere to go. • Decorated coroutines: – have additional integration with the concurrent.futures package, allowing the result of executor. submit to be yielded directly. For native coroutines, use IOLoop singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary of impossible for a clear_all_cookies method to work reliably since all we know about cookies are their names. Applications should generally use clear_cookie one at a time instead. RequestHandler.get_signed_cookie(name:

somewhere to go. • Decorated coroutines: – have additional integration with the concurrent.futures package, allowing the result of executor. submit to be yielded directly. For native coroutines, use IOLoop singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary of impossible for a clear_all_cookies method to work reliably since all we know about cookies are their names. Applications should generally use clear_cookie one at a time instead. RequestHandler.get_signed_cookie(name:

somewhere to go. • Decorated coroutines: – have additional integration with the concurrent.futures package, allowing the result of executor. submit to be yielded directly. For native coroutines, use IOLoop singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary of impossible for a clear_all_cookies method to work reliably since all we know about cookies are their names. Applications should generally use clear_cookie one at a time instead. RequestHandler.get_signed_cookie(name:

somewhere to go. • Decorated coroutines: – have additional integration with the concurrent.futures package, allowing the result of executor. submit to be yielded directly. For native coroutines, use IOLoop singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary of impossible for a clear_all_cookies method to work reliably since all we know about cookies are their names. Applications should generally use clear_cookie one at a time instead. RequestHandler.get_signed_cookie(name:

somewhere to go. • Decorated coroutines: – have additional integration with the concurrent.futures package, allowing the result of executor. submit to be yielded directly. For native coroutines, use IOLoop singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary of RequestHandler, which load templates automatically based on the template_path Application setting. Variable names beginning with _tt_ are reserved by the template system and should not be used by application code

somewhere to go. • Decorated coroutines: – have additional integration with the concurrent.futures package, allowing the result of executor. submit to be yielded directly. For native coroutines, use IOLoop singular counterparts. Files uploaded via a form are available in self.request.files, which maps names (the name of the HTML element) to a list of files. Each file is a dictionary of impossible for a clear_all_cookies method to work reliably since all we know about cookies are their names. Applications should generally use clear_cookie one at a time instead. 6.2. Web framework 47Tornado