Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
gh-100160: Restore and deprecate implicit creation of an event loop#100410
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
gh-100160: Restore and deprecate implicit creation of an event loop#100410
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Partially revert changes made inpythonGH-93453.asyncio.DefaultEventLoopPolicy.get_event_loop() now emits aDeprecationWarning and creates and sets a new event loop instead ofraising a RuntimeError if there is no current event loop set.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Misc/NEWS.d/next/Library/2022-12-21-17-49-50.gh-issue-100160.N0NHRj.rst OutdatedShow resolvedHide resolved
Uh oh!
There was an error while loading.Please reload this page.
Co-authored-by: Guido van Rossum <gvanrossum@gmail.com>
…chaka/cpython into asyncio-get_event_loop3-3.12
Uh oh!
There was an error while loading.Please reload this page.
Partially revert changes made inGH-93453.
asyncio.DefaultEventLoopPolicy.get_event_loop() now emits a DeprecationWarning and creates and sets a new event loop instead of raising a RuntimeError if there is no current event loop set.