bpo-34430: double chaining futures in asyncio.wrap_future #8804
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.
asyncio.future.wrap_future is used to wrap a concurrent.future.Future in a asyncio.future.Future.
The actual implementation as the following behaviours :
I wonder why the futures synchronisation is not symmetrical ?
I propose to add the following behaviours :
If there is good reasons to not implement the proposed behaviours, I would be glad to know.
Thank you !
https://bugs.python.org/issue34430