Closed kumaraditya303 closed 3 weeks ago
(FTR: type-feature automatically implies main
: https://devguide.python.org/triage/labels/#type-labels)
Is there a discussion somewhere about moving forward with this removal for 3.14? Is there a particular reason to move forward with this removal in 3.14, following the minimum deprecated->removed delay that the deprecation policy allows?
What are the downsides of deferring this removal a bit longer?
Even the docs are not prescriptive about the removal coming up in 3.14 :) :
... In some future Python release this will become an error.
For context, while I'm generally in favor of acting on deprecations, I am somewhat concerned that this specific one will be quite disruptive.
I regularly come across code with plenty of bad patterns around asyncio usage, with the reliance on get_event_loop
always returning a loop being one of the more common patterns. It could be beneficial to let the deprecation bake for several more releases before acting on the removal, unless there are other compelling reasons to go ahead with the removal sooner rather than later.
cc @fried maybe you can double check my concerns and let me know if I'm being too conservative with this one.
Searching the top 8k PyPI projects (downloaded April 2024) found 1,904 matching lines in 391 projects for asyncio.get_event_loop
:
Is there a discussion somewhere about moving forward with this removal for 3.14? Is there a particular reason to move forward with this removal in 3.14, following the minimum deprecated->removed delay that the deprecation policy allows?
See asyncio channel on discord. I have given reasons for it there.
Please also summarise here, not everyone is on the private Discord.
Summary:
Remove implicit creation of event loop from
asyncio.get_event_loop
as deprecated from Python 3.12.Linked PRs