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-09.15:49:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> If you're worried about blocking the event loop just to acquire the threading lock that's part of threading.Event, you can use run_in_executor()

I'm more worried to delay invocation of a "synchronous" report because of outstanding tasks in event loop's queue. Given my situtation, that may not even happen because outstanding tasks may stop the loop by raising their own exceptions.

I'm willing to sacrifice them (i.e. I'm ok with not sending them) in order to send information about exception "for sure".
Date User Action Args
2016-05-09 15:49:50Ilya.Kulakovsetrecipients: + Ilya.Kulakov, gvanrossum, vstinner, r.david.murray, yselivanov
2016-05-09 15:49:50Ilya.Kulakovsetmessageid: <>
2016-05-09 15:49:50Ilya.Kulakovlinkissue26969 messages
2016-05-09 15:49:49Ilya.Kulakovcreate