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 yselivanov
Recipients Ilya.Kulakov, gvanrossum, r.david.murray, vstinner, yselivanov
Date 2016-05-10.20:42:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
>> I now think that we don't need a new function for getting the currently running event loop.

> May I ask you to elaborate on this?

In my last message I propose to modify 'get_event_loop' to return the running loop reliably.  To me this is to me the most important thing -- this will make things like Task.current more reliable.

Adding another function (get_running_loop) won't change much. It would have a slightly different behaviour, but likely it won't be used anywhere in asyncio, or other libraries.
Date User Action Args
2016-05-10 20:42:46yselivanovsetrecipients: + yselivanov, gvanrossum, vstinner, r.david.murray, Ilya.Kulakov
2016-05-10 20:42:46yselivanovsetmessageid: <>
2016-05-10 20:42:46yselivanovlinkissue26969 messages
2016-05-10 20:42:46yselivanovcreate