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 asvetlov
Recipients Ben.Darnell, aeros, asvetlov, minrk, serhiy.storchaka, xtreak, yselivanov
Date 2021-12-01.12:23:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1638361420.23.0.122795208504.issue39529@roundup.psfhosted.org>
In-reply-to
Content
Ages ago, get_event_loop() did not return the current running loop if called from async function context; it returned a loop instance registered with previous set_event_loop(...) call instead.

Later we fixed get_event_loop() behavior in 3.5.4 IIRC and added get_running_loop() in 3.7

set_event_loop() doesn't make sense now from my perspective.
History
Date User Action Args
2021-12-01 12:23:40asvetlovsetrecipients: + asvetlov, Ben.Darnell, serhiy.storchaka, yselivanov, minrk, xtreak, aeros
2021-12-01 12:23:40asvetlovsetmessageid: <1638361420.23.0.122795208504.issue39529@roundup.psfhosted.org>
2021-12-01 12:23:40asvetlovlinkissue39529 messages
2021-12-01 12:23:40asvetlovcreate