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 Ilya.Kulakov
Recipients Ilya.Kulakov, gvanrossum, r.david.murray, vstinner, yselivanov
Date 2016-05-10.20:36:52
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? Asynchronous API I'm aware of (including  other languages) typically allows to get "main" (which in asyncio is lazily created for main thread only), and "current". Sometimes there is also a convenient "global" which can be used when you want to do some async work outside. E.g. take a look at public API of Apple's Grand Central Dispatch, specifically `dispatch_get_current_queue`.

Even Python's thread module allows to get "current_thread" instead of passing it into run callback and requiring a user to carry it around by hand.
Date User Action Args
2016-05-10 20:36:53Ilya.Kulakovsetrecipients: + Ilya.Kulakov, gvanrossum, vstinner, r.david.murray, yselivanov
2016-05-10 20:36:53Ilya.Kulakovsetmessageid: <>
2016-05-10 20:36:53Ilya.Kulakovlinkissue26969 messages
2016-05-10 20:36:52Ilya.Kulakovcreate