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-06.20:02:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Probably it would make sense to modify behavior of the default policy to make get_event_loop to return Thread-local event loop when called from out-of-event-loop and return currently running event loop when called from within a coroutine.

The problem with this approach is that you're relying on the presence of GIL.  If, let's say, PyPy releases tomorrow with 3.5 and STM, this won't work.
Date User Action Args
2016-05-06 20:02:39yselivanovsetrecipients: + yselivanov, gvanrossum, vstinner, r.david.murray, Ilya.Kulakov
2016-05-06 20:02:39yselivanovsetmessageid: <>
2016-05-06 20:02:39yselivanovlinkissue26969 messages
2016-05-06 20:02:39yselivanovcreate