René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"DeprecationWarning scope expanded in asyncio.events","articleBody":"As discovered in https://github.com/prompt-toolkit/python-prompt-toolkit/issues/1696, it appears that the DeprecationWarning introduced in Python 3.10 has expanded its scope, now with 3.11.1 and 3.10.9 emitting during get_event_loop_policy() where it did not before:\r\n\r\n```\r\n ~ $ py -3.11 -W error\r\nPython 3.11.0 (main, Oct 26 2022, 19:06:18) [Clang 14.0.0 (clang-1400.0.29.202)] on darwin\r\nType \"help\", \"copyright\", \"credits\" or \"license\" for more information.\r\n\u003e\u003e\u003e import asyncio\r\n\u003e\u003e\u003e asyncio.get_event_loop_policy().get_event_loop()\r\n\u003c_UnixSelectorEventLoop running=False closed=False debug=False\u003e\r\n\u003e\u003e\u003e ^D\r\n ~ $ docker run -it jaraco/multipy-tox py -3.11 -W error\r\nPython 3.11.1 (main, Dec  7 2022, 01:11:34) [GCC 11.3.0] on linux\r\nType \"help\", \"copyright\", \"credits\" or \"license\" for more information.\r\n\u003e\u003e\u003e import asyncio\r\n\u003e\u003e\u003e asyncio.get_event_loop_policy().get_event_loop()\r\nTraceback (most recent call last):\r\n  File \"\u003cstdin\u003e\", line 1, in \u003cmodule\u003e\r\n  File \"/usr/lib/python3.11/asyncio/events.py\", line 687, in get_event_loop\r\n    warnings.warn('There is no current event loop',\r\nDeprecationWarning: There is no current event loop\r\n```\r\n\r\nIt's not obvious if it was intentional to expand the scope of the DeprecationWarning, but it does come as a surprise as the calling code had previously attempted to address the deprecation.\r\n\r\nI think there are two concerns to be addressed:\r\n\r\n- Does this symptom indicate an unintentional but real additional path that was previously unprotected by the DeprecationWarning? And if so, does that imply that the behavior's first true deprecation is in Python 3.12 and thus will delay the removal?\r\n- What is a user expected to do to properly address the deprecation? I read the [what's new for Python 3.10](https://docs.python.org/3/whatsnew/3.10.html) and it indicates that the call is deprecated, but it provides little guidance on how a user can adapt to the new behavior. Maybe there should be a note to the effect of \"programs relying on a non-running event loop must ensure that there is a running event loop before attempting to get the event loop.\"\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-100410\n* gh-100412\n* gh-100969\n* gh-100970\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/jaraco","@type":"Person","name":"jaraco"},"datePublished":"2022-12-10T14:02:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":28},"url":"https://github.com/100160/cpython/issues/100160"}