Clears the IOLoop for the current thread. Intended primarily for use by test frameworks in between tests. Changed in version 5.0: This method also clears the current asyncio event loop. IOLoop.start() be cleaned up when the process exits. IOLoop.close is provided mainly for scenarios such as unit tests, which create and destroy a large number of IOLoops. An IOLoop must be completely stopped before TornadoReactor(). However, if the IOLoop and reactor are to be short-lived (such as those used in unit tests), additional cleanup may be required. Specifically, it is recommended to call: reactor.fireSystemEvent('shutdown')

Clears the IOLoop for the current thread. Intended primarily for use by test frameworks in between tests. Changed in version 5.0: This method also clears the current asyncio event loop. IOLoop.start() be cleaned up when the process exits. IOLoop.close is provided mainly for scenarios such as unit tests, which create and destroy a large number of IOLoops. An IOLoop must be completely stopped before restart the process. Intended to be used at the end of scripts like unit test runners, to run the tests again after any source file changes (but see also the command-line interface in main) 6.7. Utilities

Clears the IOLoop for the current thread. Intended primarily for use by test frameworks in between tests. Changed in version 5.0: This method also clears the current asyncio event loop. IOLoop.start() be cleaned up when the process exits. IOLoop.close is provided mainly for scenarios such as unit tests, which create and destroy a large number of IOLoops. An IOLoop must be completely stopped before restart the process. Intended to be used at the end of scripts like unit test runners, to run the tests again after any source file changes (but see also the command-line interface in main) 134 Chapter

Clears the IOLoop for the current thread. Intended primarily for use by test frameworks in between tests. Changed in version 5.0: This method also clears the current asyncio [https://docs.python.org/3 be cleaned up when the process exits. IOLoop.close is provided mainly for scenarios such as unit tests, which create and destroy a large number of IOLoops. An IOLoop must be completely stopped before TornadoReactor(). However, if the IOLoop and reactor are to be short-lived (such as those used in unit tests), additional cleanup may be required. Specifically, it is recommended to call: reactor.fireSystemEvent('shutdown')

Clears the IOLoop for the current thread. Intended primarily for use by test frameworks in between tests. Changed in version 5.0: This method also clears the current asyncio event loop. Deprecated since be cleaned up when the process exits. IOLoop.close is provided mainly for scenarios such as unit tests, which create and destroy a large number of IOLoops. An IOLoop must be completely stopped before restart the process. Intended to be used at the end of scripts like unit test runners, to run the tests again after any source file changes (but see also the command-line interface in main) tornado.autoreload

Clears the IOLoop for the current thread. Intended primarily for use by test frameworks in between tests. Changed in version 5.0: This method also clears the current asyncio event loop. Deprecated since be cleaned up when the process exits. IOLoop.close is provided mainly for scenarios such as unit tests, which create and destroy a large number of IOLoops. An IOLoop must be completely stopped before restart the process. Intended to be used at the end of scripts like unit test runners, to run the tests again after any source file changes (but see also the command-line interface in main) tornado.autoreload

Clears the IOLoop for the current thread. Intended primarily for use by test frameworks in between tests. Changed in version 5.0: This method also clears the current asyncio event loop. Deprecated since be cleaned up when the process exits. IOLoop.close is provided mainly for scenarios such as unit tests, which create and destroy a large number of IOLoops. An IOLoop must be completely stopped before restart the process. Intended to be used at the end of scripts like unit test runners, to run the tests again after any source file changes (but see also the command-line interface in main) tornado.autoreload

Clears the IOLoop for the current thread. Intended primarily for use by test frameworks in between tests. Changed in version 5.0: This method also clears the current asyncio event loop. Deprecated since be cleaned up when the process exits. IOLoop.close is provided mainly for scenarios such as unit tests, which create and destroy a large number of IOLoops. An IOLoop must be completely stopped before restart the process. Intended to be used at the end of scripts like unit test runners, to run the tests again after any source file changes (but see also the command-line interface in main) tornado.autoreload

Clears the IOLoop for the current thread. Intended primarily for use by test frameworks in between tests. Changed in version 5.0: This method also clears the current asyncio event loop. Deprecated since be cleaned up when the process exits. IOLoop.close is provided mainly for scenarios such as unit tests, which create and destroy a large number of IOLoops. An IOLoop must be completely stopped before restart the process. Intended to be used at the end of scripts like unit test runners, to run the tests again after any source file changes (but see also the command-line interface in main) tornado.autoreload

Clears the IOLoop for the current thread. Intended primarily for use by test frameworks in between tests. Changed in version 5.0: This method also clears the current asyncio event loop. Deprecated since be cleaned up when the process exits. IOLoop.close is provided mainly for scenarios such as unit tests, which create and destroy a large number of IOLoops. An IOLoop must be completely stopped before restart the process. Intended to be used at the end of scripts like unit test runners, to run the tests again after any source file changes (but see also the command-line interface in main) tornado.autoreload