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-06.20:09:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> In this case I'm not sure how this is different from the current "get_event_loop"

Thread may have multiple event loops, but only one, explicitly associated, is default. And it's not necessary one which is currently running.

I think what I propose here can be expressed in Python terms as an implicit context manager that replaces Thread's default event loop once while it "runs" particular event loop then switches it back (possible to None) once loop is stopped.
Date User Action Args
2016-05-06 20:09:48Ilya.Kulakovsetrecipients: + Ilya.Kulakov, gvanrossum, vstinner, r.david.murray, yselivanov
2016-05-06 20:09:48Ilya.Kulakovsetmessageid: <>
2016-05-06 20:09:48Ilya.Kulakovlinkissue26969 messages
2016-05-06 20:09:48Ilya.Kulakovcreate