Skip to content

gh-83852: Clarify semantics of asyncio.wait with FIRST_COMPLETED/EXCEPTION #21918

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
embray wants to merge 2 commits into from
Closed

gh-83852: Clarify semantics of asyncio.wait with FIRST_COMPLETED/EXCEPTION #21918

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2783ae8
Clarify semantics of asyncio.wait with FIRST_COMPLETED/EXCEPTION
embray Aug 18, 2020
2773593
Merge branch 'main' into patch-1
willingc Apr 26, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions Doc/library/asyncio-task.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -797,6 +797,11 @@ Waiting Primitives
| :const:`ALL_COMPLETED` | The function will return when all |
| | futures finish or are cancelled. |
+-----------------------------+----------------------------------------+

Using ``return_when=FIRST_COMPLETED`` or ``return_when=FIRST_EXCEPTION``
does *not* imply that the ``done`` set will contain only the first
finished future, as multiple futures may finish before the function
returns.

Unlike :func:`~asyncio.wait_for`, ``wait()`` does not cancel the
futures when a timeout occurs.
Expand Down