Add asyncio.graph, updates to asyncio.futures (3.14)#14003
Merged
srittau merged 14 commits intopython:mainfrom May 12, 2025
Merged
Add asyncio.graph, updates to asyncio.futures (3.14)#14003srittau merged 14 commits intopython:mainfrom
asyncio.graph, updates to asyncio.futures (3.14)#14003srittau merged 14 commits intopython:mainfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Add new
asyncio.graphmodule and made updates forasyncio.futuresDidn't fix all issues because surprisingly (at least to me) some private functions were added to
asyncio.events.__all__, take_get_event_loop_policyto accomadate deprecations, see this PR as an example: python/cpython#128218. Once we tackle adding these, I don't think it necessarily makes sense to add them considering they'll be both private and deprecated on addition. Perhaps this is something to change in cpython itself.