-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
gh-94597: deprecate asyncio.set_event_loop_policy #110728
base: main
Are you sure you want to change the base?
Conversation
a7fe31c
to
339445e
Compare
f7a1b68
to
491b42e
Compare
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.
No objection to the unittest or AsyncMock changes!
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.
Just a few nits, basically LG. That tearDownModule()
pattern is annoying! :-)
I assume that deprecating get_event_loop_policy()
will follow? Are there other APIs? I'm guessing we also want to avoid instantiating or subclassing the standard event loop policy classes (I expect this will turn up some significant uses of them).
Before we merge this we may need to bring this up on discuss.python.org (in the asyncio category) to see if there are significant objections to the proposed deprecation schedule.
Misc/NEWS.d/next/Library/2023-10-11-15-55-53.gh-issue-94597.qXo8Q4.rst
Outdated
Show resolved
Hide resolved
…o8Q4.rst Co-authored-by: Guido van Rossum <[email protected]>
I think we can start getting rid of those tearDownModules using #110774
Yep currently that's a bit more complicated because get/set_event_loop calls get_event_loop_policy and afaik we don't want to make get_event_loop an alias of get_running_loop anymore |
Please also mention the deprecation in What's New in Python 3.13. Because it's to be removed in 3.15 or later it could be listed under either Pending Removal in Python 3.15 or Pending Removal in Future Versions. I suggest the former, as it's more likely to be noticed and action taken, and include the "3.15 or later" wording. We can update later if needed. |
Co-authored-by: Hugo van Kemenade <[email protected]>
discuss post posted here: https://discuss.python.org/t/removing-the-asyncio-policy-system-asyncio-set-event-loop-policy-in-python-3-15/37553 |
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.
Okay, I'm happy with this. Let's wait a bit if anyone brings up substantial objections in the Discourse thread.
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.
Bravo @graingert for simplifying. ✨
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.
Please also add a notice under asyncio
changes, most users like myself won't look under 3.15 removals for this change. Thanks
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase And if you don't make the requested changes, you will be poked with soft cushions! |
Can you link me to the location in the docs that you mean please? |
Add |
That sounds fine, then let's move it from the "Pending Removal in Python 3.15" section to this one. |
I have made the requested changes; please review again |
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.
LGTM, but let's wait until the dust in the Discourse thread settles.
Happy to review and hopefully merge this during the core sprint. |
📚 Documentation preview 📚: https://cpython-previews--110728.org.readthedocs.build/