This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author wwallace
Recipients aeros, asvetlov, njs, wwallace, yselivanov
Date 2020-06-29.15:39:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1593445167.06.0.164375364559.issue39085@roundup.psfhosted.org>
In-reply-to
Content
There are a few other places on the documentation that are imprecise or misleading for await. While the information needed is scattered around the docs, I think these can also be improved. I'm pretty sure these fit with this issue.

Developing with asyncio guide:
https://docs.python.org/3/library/asyncio-dev.html#concurrency-and-multithreading - first paragraph, "When a Task executes an await expression, the running Task gets suspended, and the event loop executes the next Task."  Taken by itself it isn't clear that execution of the awaitable starts immediately without intervention from the event loop. A possible fix might be to add "If the awaited expression is a coroutine its execution begins immediately and the  running Task will not suspend till the awaited expression stalls waiting for a result." 

The same sentence is found in the Task documentation: https://docs.python.org/3/library/asyncio-task.html#task-object
History
Date User Action Args
2020-06-29 15:39:27wwallacesetrecipients: + wwallace, njs, asvetlov, yselivanov, aeros
2020-06-29 15:39:27wwallacesetmessageid: <1593445167.06.0.164375364559.issue39085@roundup.psfhosted.org>
2020-06-29 15:39:27wwallacelinkissue39085 messages
2020-06-29 15:39:26wwallacecreate