René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"asyncio: Re-reverse deprecation of set_event_loop?","articleBody":"# Feature or enhancement\n\n### Proposal:\n\nThe asyncio policy system is deprecated in python 3.14 (#127949). As implemented, this includes the `asyncio.set_event_loop()` function. However, in 2022,  [it was decided](https://github.com/python/cpython/pull/98440#issuecomment-1334030286) that `set_event_loop` and `get_event_loop` (just the thread-local storage, not the broader policy system) were serving a useful and separate purpose and should be kept around. I [relied on this decision](https://github.com/tornadoweb/tornado/issues/3216) in Tornado to adapt to various changes while staying on interfaces that I thought would be safe from deprecation. \n\nI would like to briefly bring this up for reconsideration since this is a reversal of a decision from just a few years ago and it appears to have been lumped in with the rest of the policy system without consideration on its own. \n\nIf the decision to deprecate this function stands, I'll be able to adapt in Tornado, but it will be inconvenient: I think I'll have to use asyncio.Runner which was introduced in 3.11, while I'm still supporting 3.9 and 3.10 for another couple of years. \n\n## Background\n\nHere's the history as I remember it. In Python 3.10, the policy system was deprecated and slated for removal in 3.12. When the 3.12 alphas were released with the policy methods removed, we found that there were code paths that relied on the deprecated methods without emitting suitable warnings, leading to surprise breakages. This caused everything to be reset (in 3.10.9 and 3.11.1, which is why those specific versions are [cited in the docs](https://docs.python.org/3.10/library/asyncio-policy.html)). Deprecation notices were removed, but the understanding at the time was that this was just resetting the clock and policies would still be going away, just a few years later. \n\nSeparately, there was a debate about the set_event_loop function, although I can't find the right thread now. (https://github.com/python/cpython/issues/83710#issuecomment-1093855418 and https://github.com/python/cpython/pull/98440#issuecomment-1334030286 are related, but I can't find where the actual conclusion was reached). I think Jupyter was another project where `set_event_loop` turned out to be important?\n\n### Has this already been discussed elsewhere?\n\nThis is a minor feature, which does not need previous discussion elsewhere\n\n### Links to previous discussion of this feature:\n\n_No response_\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-132349\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/bdarnell","@type":"Person","name":"bdarnell"},"datePublished":"2025-02-19T20:46:23.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":13},"url":"https://github.com/130322/cpython/issues/130322"}