This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author erlendaasland
Recipients asvetlov, erlendaasland, kumaraditya, yselivanov
Date 2022-01-11.08:45:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1641890734.7.0.240445368406.issue46340@roundup.psfhosted.org>
In-reply-to
Content
Providing some more background, based on the changes proposed by Kumar in GH-30486:

asyncio.get_event_loop() was marked as deprecated in Python 3.10. Quoting from the asyncio documentation , https://docs.python.org/3/library/asyncio-eventloop.html (as of 3.10):

    Because this function has rather complex behavior (especially when custom
    event loop policies are in use), using the get_running_loop() function is
    preferred to get_event_loop() in coroutines and callbacks.

    [...]

    Deprecated since version 3.10: Deprecation warning is emitted if there is
    no running event loop. In future Python releases, this function will be an
    alias of get_running_loop().


GH-30486 proposes to replace asyncio.get_event_loop() with asyncio.new_event_loop().
History
Date User Action Args
2022-01-11 08:45:34erlendaaslandsetrecipients: + erlendaasland, asvetlov, yselivanov, kumaraditya
2022-01-11 08:45:34erlendaaslandsetmessageid: <1641890734.7.0.240445368406.issue46340@roundup.psfhosted.org>
2022-01-11 08:45:34erlendaaslandlinkissue46340 messages
2022-01-11 08:45:34erlendaaslandcreate