ambiguous as to whether an argument is a single value or a list with one element, RequestHandler has distinct methods to allow the application to indicate whether or not it expects a list. For lists, use get_query_arguments via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the global template namespace and their it returns is available, only that a series of get_unused_port calls in a single process return distinct ports. Deprecated since version Use: bind_unused_port instead, which is guaranteed to find an unused

ambiguous as to whether an argument is a single value or a list with one element, RequestHandler has distinct methods to allow the application to indicate whether or not it expects a list. For lists, use get_query_arguments via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the global template namespace and their it returns is available, only that a series of get_unused_port calls in a single process return distinct ports. Deprecated since version Use: bind_unused_port instead, which is guaranteed to find an unused

ambiguous as to whether an argument is a single value or a list with one element, RequestHandler has distinct methods to allow the application to indicate whether or not it expects a list. For lists, use get_query_arguments via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the global template namespace and their and IOLoop.clear_current are deprecated. In the future the concept of a “current” event loop as distinct from one that is currently running will be removed. • TwistedResolver and CaresResolver are deprecated

ambiguous as to whether an argument is a single value or a list with one element, RequestHandler has distinct methods to allow the application to indicate whether or not it expects a list. For lists, use get_query_arguments via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the global template namespace and their and IOLoop.clear_current are deprecated. In the future the concept of a “current” event loop as distinct from one that is currently running will be removed. • TwistedResolver and CaresResolver are deprecated

ambiguous as to whether an argument is a single value or a list with one element, RequestHandler has distinct methods to allow the application to indicate whether or not it expects a list. For lists, use get_query_arguments via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the global template namespace and their and IOLoop.clear_current are deprecated. In the future the concept of a “current” event loop as distinct from one that is currently running will be removed. • TwistedResolver and CaresResolver are deprecated

ambiguous as to whether an argument is a single value or a list with one element, RequestHandler has distinct methods to allow the application to indicate whether or not it expects a list. For lists, use get_query_arguments via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the global template namespace and their and IOLoop.clear_current are deprecated. In the future the concept of a “current” event loop as distinct from one that is currently running will be removed. • TwistedResolver and CaresResolver are deprecated

ambiguous as to whether an argument is a single value or a list with one element, RequestHandler has distinct methods to allow the application to indicate whether or not it expects a list. For lists, use get_query_arguments via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the global template namespace and their and IOLoop.clear_current are deprecated. In the future the concept of a “current” event loop as distinct from one that is currently running will be removed. • TwistedResolver and CaresResolver are deprecated

ambiguous as to whether an argument is a single value or a list with one element, RequestHandler has distinct methods to allow the application to indicate whether or not it expects a list. For lists, use get_query_arguments via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the global template namespace and their and IOLoop.clear_current are deprecated. In the future the concept of a “current” event loop as distinct from one that is currently running will be removed. • TwistedResolver and CaresResolver are deprecated

ambiguous as to whether an argument is a single value or a list with one element, RequestHandler has distinct methods to allow the application to indicate whether or not it expects a list. For lists, use get_query_arguments via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the global template namespace and their and IOLoop.clear_current are deprecated. In the future the concept of a “current” event loop as distinct from one that is currently running will be removed. TwistedResolver and CaresResolver are deprecated

ambiguous as to whether an argument is a single value or a list with one element, RequestHandler has distinct methods to allow the application to indicate whether or not it expects a list. For lists, use get_query_arguments via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the global template namespace and their than the default. • The IOLoop poller implementations (select, epoll, kqueue) are now available as distinct subclasses of IOLoop. Instantiating IOLoop will continue to automatically choose the best available