From 70db9e428aa476682ca80369d09a968b35729845 Mon Sep 17 00:00:00 2001 From: Victor Stinner Date: Fri, 9 Jan 2015 21:32:05 +0100 Subject: asyncio: sync with Tulip * Tulip issue 184: FlowControlMixin constructor now get the event loop if the loop parameter is not set. Add unit tests to ensure that constructor of StreamReader and StreamReaderProtocol classes get the event loop. * Remove outdated TODO/XXX --- Lib/asyncio/futures.py | 2 -- 1 file changed, 2 deletions(-) (limited to 'Lib/asyncio/futures.py') diff --git a/Lib/asyncio/futures.py b/Lib/asyncio/futures.py index f46d008f08..e0e12f0579 100644 --- a/Lib/asyncio/futures.py +++ b/Lib/asyncio/futures.py @@ -20,7 +20,6 @@ _FINISHED = 'FINISHED' _PY34 = sys.version_info >= (3, 4) -# TODO: Do we really want to depend on concurrent.futures internals? Error = concurrent.futures._base.Error CancelledError = concurrent.futures.CancelledError TimeoutError = concurrent.futures.TimeoutError @@ -30,7 +29,6 @@ STACK_DEBUG = logging.DEBUG - 1 # heavy-duty debugging class InvalidStateError(Error): """The operation is not allowed in this state.""" - # TODO: Show the future, its state, the method, and the required state. class _TracebackLogger: -- cgit v1.2.1