-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
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.
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
bpo-38599: Deprecate creation of asyncio object when the loop is not running #18195
Closed
Closed
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
2941d1e
Deprecate creation of asyncio object when the loop is not running
eamanu 7958de9
Add NEWS
eamanu 976a808
Fix Deprecation Warning message.
eamanu 44fa5f6
Remove change on BoundedSemaphore
eamanu e486fe4
add test
eamanu bae5755
Merge branch 'master' into fix-38599
eamanu 18c4ddf
Fix tests
eamanu dc78f3a
Fix PR according to @aeros comments
eamanu 1bb46a8
Fix according to review comments
eamanu 0ca9f61
remove assertWarns on where is not applied
eamanu c4afc8f
Update Lib/asyncio/locks.py
eamanu ec3a6aa
fix grammar error
eamanu dd6dec3
Remove assertWarns not applied on queues test
eamanu c5d332a
Merge branch 'fix-38599' of github.com:eamanu/cpython into fix-38599
eamanu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be very confusing to users to add a deprecation warning in 3.8, and then remove the warning from certain asyncio objects entirely in 3.9. That doesn't make much sense to me.
(also applies to the other warning removals)