From 86e139ad655df3650e138276a03a7e2bff706684 Mon Sep 17 00:00:00 2001 From: Victor Stinner Date: Fri, 13 Dec 2013 12:51:24 +0100 Subject: [PATCH] asyncio doc: explain where does the task come from. --- Doc/library/asyncio-task.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/Doc/library/asyncio-task.rst b/Doc/library/asyncio-task.rst index 83612574021..adc344e2168 100644 --- a/Doc/library/asyncio-task.rst +++ b/Doc/library/asyncio-task.rst @@ -108,10 +108,12 @@ Sequence diagram of the example: .. image:: tulip_coro.png :align: center -The diagram shows the logical links between the task and the two coroutines, it -does not describe exactly how things work internally. For example, the sleep -coroutine creates an internal future which uses -:meth:`BaseEventLoop.call_later` to wake up the task in 1 second. +The "Task" is created by the :meth:`BaseEventLoop.run_until_complete` method +when it gets a coroutine instead of a task. + +The diagram shows the control flow, it does not describe exactly how things +work internally. For example, the sleep coroutine creates an internal future +which uses :meth:`BaseEventLoop.call_later` to wake up the task in 1 second. InvalidStateError