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.

Title: asyncio.wait documentation on non-emptiness requirement lost in bpo-33649
Type: Stage: resolved
Components: Documentation Versions: Python 3.9, Python 3.8, Python 3.7
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: docs@python Nosy List: Joel Rosdahl, docs@python, gvanrossum, jrosdahl
Priority: normal Keywords: patch

Created on 2020-05-04 12:16 by Joel Rosdahl, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 19900 merged jrosdahl, 2020-05-04 12:24
Messages (2)
msg368041 - (view) Author: Joel Rosdahl (Joel Rosdahl) Date: 2020-05-04 12:16
bpo-21596 documented that the sequence of futures passed to asyncio.wait must not be empty:

    The sequence *futures* must not be empty.

This note was however lost in the bpo-33649 commit
msg368091 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2020-05-04 21:56
New changeset 9d74658f0a6e8a9b8d6dcf199dda886f35c6ad68 by Joel Rosdahl in branch 'master':
bpo-40499: Mention that asyncio.wait() needs a non-empty aws set (GH-19900)
Date User Action Args
2022-04-11 14:59:30adminsetgithub: 84679
2020-05-04 21:56:50gvanrossumsetstatus: open -> closed
resolution: fixed
stage: patch review -> resolved
2020-05-04 21:56:08gvanrossumsetnosy: + gvanrossum
messages: + msg368091
2020-05-04 12:24:52jrosdahlsetkeywords: + patch
nosy: + jrosdahl

pull_requests: + pull_request19211
stage: patch review
2020-05-04 12:16:17Joel Rosdahlcreate