[3.7] bpo-37658: Fix asyncio.wait_for() to respect waited task status (GH-21894) #21969
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…pythonGH-21894) Currently, if `asyncio.wait_for()` itself is cancelled it will always raise `CancelledError` regardless if the underlying task is still running. This is similar to a race with the timeout, which is handled already.. (cherry picked from commit a2118a1) Co-authored-by: Elvis Pranskevichus <[email protected]>
1st1
approved these changes
Aug 26, 2020
|
@ambv I don't think I can merge this on my own... |
|
@1st1 it's because 3.7 is in "security bug fixes only" mode now. 3.7.9 last week was the last regular bugfix release, and even that was an extended release courtesy of Ned. I don't think 3.7 will be getting this. |
|
ah, sure. Closing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, if
asyncio.wait_for()itself is cancelled it will alwaysraise
CancelledErrorregardless if the underlying task is stillrunning. This is similar to a race with the timeout, which is handled
already..
(cherry picked from commit a2118a1)
https://bugs.python.org/issue37658