Repository navigation
asyncio.wait_for() docs still say a coroutine is wrapped in a Task #155894
Description
Documentation
Since 3.12 asyncio.wait_for() no longer wraps a coroutine in a Task for positive timeouts, but the docs still say it does
Where the docs are misleading:
Doc/library/asyncio-task.rst:846 — "If fut is a coroutine it is automatically scheduled as a Task."
Lib/asyncio/tasks.py:443 — "Coroutine will be wrapped in Task."
:846-855 also refer to "the task" that does not exist, and there is no versionchanged:: 3.12.
Linked PRs
- gh-155894: Fix wait_for() docs claiming a coroutine is wrapped in a Task #155895
- [3.15] gh-155894: Fix wait_for() docs claiming a coroutine is wrapped in a Task #156038
- [3.14] gh-155894: Fix wait_for() docs claiming a coroutine is wrapped in a Task #156039
- [3.13] gh-155894: Fix wait_for() docs claiming a coroutine is wrapped in a Task #156045
Activity
kumaraditya303 commentedon Aug 17, 2026
I don't think it is useful to document if a task gets created or not here, maybe just remove that line altogether?
deadlovelll commentedon Aug 17, 2026
I proceeded on the assumption that a previously documented implementation detail should stay documented. In any case, I agree. I just pushed the changes
Merge branch 'main' into pythongh-155894-doc-issue
gh-155894: Fix asyncio.wait_for() docs claiming a coroutine is wrappe…
[3.13] gh-155894: Fix wait_for() docs claiming a coroutine is wrapped…
[3.14] gh-155894: Fix wait_for() docs claiming a coroutine is wrapped…
[3.15] gh-155894: Fix wait_for() docs claiming a coroutine is wrapped…