Command-line parsing tornado.stack_context — Exception handling across asynchronous callbacks tornado.testing — Unit testing support for asynchronous code tornado.util — General-purpose utilities Frequently OptionParser class tornado.stack_context — Exception handling across asynchronous callbacks tornado.testing — Unit testing support for asynchronous code Asynchronous test cases Controlling log output correct(): yield run_with_stack_context(StackContext(ctx), other_coroutine) New in version 3.1. tornado.testing — Unit testing support for asynchronous code Support classes for automated testing. AsyncTestCase

= Application( handlers, **options.group_dict('application')) Added in version 3.1. 6.7.5 tornado.testing — Unit testing support for asynchronous code Support classes for automated testing. • AsyncTestCase run with any test runner. The easiest way to run a test is via the command line: python -m tornado.testing tornado.test.web_test See the standard library unittest module for ways in which tests can be carriage return characters in HTTP headers. It had previously prohibited only linefeed characters. tornado.testing • AsyncTestCase subclasses can now be instantiated without being associated with a test method

application = Application( handlers, **options.group_dict('application')) New in version 3.1. 6.7.5 tornado.testing — Unit testing support for asynchronous code Support classes for automated testing. • AsyncTestCase run with any test runner. The easiest way to run a test is via the command line: python -m tornado.testing tornado.test.web_test See the standard library unittest module for ways in which tests can be on the main thread) tornado.platform.auto • The set_close_exec function has been removed. tornado.testing • ExpectLog now has a level argument to ensure that the given log level is enabled. tornado

application = Application( handlers, **options.group_dict('application')) New in version 3.1. 6.7.5 tornado.testing — Unit testing support for asynchronous code Support classes for automated testing. • AsyncTestCase run with any test runner. The easiest way to run a test is via the command line: python -m tornado.testing tornado.test.web_test See the standard library unittest module for ways in which tests can be tcpserver • TCPServer.listen now supports more arguments to pass through to netutil.bind_sockets. tornado.testing • bind_unused_port now takes an optional address argument. • Wrapped test methods now include

New in version 3.1. 152 Chapter 6. Documentation Tornado Documentation, Release 6.2 6.7.5 tornado.testing — Unit testing support for asynchronous code Support classes for automated testing. • AsyncTestCase run with any test runner. The easiest way to run a test is via the command line: python -m tornado.testing tornado.test.web_test See the standard library unittest module for ways in which tests can be tcpserver • TCPServer.listen now supports more arguments to pass through to netutil.bind_sockets. tornado.testing • bind_unused_port now takes an optional address argument. • Wrapped test methods now include

application = Application( handlers, **options.group_dict('application')) New in version 3.1. 6.7.5 tornado.testing — Unit testing support for asynchronous code Support classes for automated testing. • AsyncTestCase run with any test runner. The easiest way to run a test is via the command line: python -m tornado.testing tornado.test.web_test See the standard library unittest module for ways in which tests can be tcpserver • TCPServer.listen now supports more arguments to pass through to netutil.bind_sockets. tornado.testing • bind_unused_port now takes an optional address argument. • Wrapped test methods now include

application = Application( handlers, **options.group_dict('application')) New in version 3.1. 6.7.5 tornado.testing — Unit testing support for asynchronous code Support classes for automated testing. • AsyncTestCase run with any test runner. The easiest way to run a test is via the command line: python -m tornado.testing tornado.test.web_test See the standard library unittest module for ways in which tests can be tcpserver • TCPServer.listen now supports more arguments to pass through to netutil.bind_sockets. tornado.testing • bind_unused_port now takes an optional address argument. • Wrapped test methods now include

application = Application( handlers, **options.group_dict('application')) New in version 3.1. 6.7.5 tornado.testing — Unit testing support for asynchronous code Support classes for automated testing. • AsyncTestCase run with any test runner. The easiest way to run a test is via the command line: python -m tornado.testing tornado.test.web_test See the standard library unittest module for ways in which tests can be tcpserver • TCPServer.listen now supports more arguments to pass through to netutil.bind_sockets. tornado.testing • bind_unused_port now takes an optional address argument. • Wrapped test methods now include

yield run_with_stack_context(StackContext(ctx), other_coroutine) New in version 3.1. 4.7.5 tornado.testing — Unit testing support for asynchronous code Support classes for automated testing. • AsyncTestCase run with any test runner. The easiest way to run a test is via the command line: python -m tornado.testing tornado.test.stack_context_test See the standard library unittest module for ways in which tests • Duplicate option names are now detected properly whether they use hyphens or underscores. tornado.testing • AsyncHTTPTestCase.fetch now uses 127.0.0.1 instead of localhost, improving compatibility with

yield run_with_stack_context(StackContext(ctx), other_coroutine) New in version 3.1. 5.7.6 tornado.testing — Unit testing support for asynchronous code Support classes for automated testing. • AsyncTestCase run with any test runner. The easiest way to run a test is via the command line: python -m tornado.testing tornado.test.stack_context_test See the standard library unittest module for ways in which tests stack_context • The tornado.stack_context module is deprecated and will be removed in 6.0. tornado.testing • AsyncHTTPTestCase.fetch now takes a raise_error argument. This argument has the same se- mantics