Author neologix
Recipients gregory.p.smith, gvanrossum, neologix
Date 2013-12-01.21:09:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM0u0BKBtV3ZZid=f1HzqpEUmsht7zdV+oHDR5ibMnvCqw@mail.gmail.com>
In-reply-to <1385926824.0.0.338852467339.issue19850@psf.upfronthosting.co.za>
Content
> It sounds like doing this is fine (as Glyph suggests in the email thread) but it isn't magically going to solve all EINTR problems, just reduce the number of calls that could encounter them.

Indeed, hence "*limit* EINTR occurrences" :-)

> Note that with this SA_RESTART flag set via siginterrupt you _may_ be making a trade off between being able to process python signal handlers during long reads or writes vs having to wait until the entire thing has finished.

asyncio uses a wakeup FD, registered in the main event loop: so as
soon as a signal is received, the main loop will wake up and run the
signal handler. So this would only be a problem if you were doing a
blocking syscall from the main loop thread, which would be a really
bad idea anyway.
History
Date User Action Args
2013-12-01 21:09:57neologixsetrecipients: + neologix, gvanrossum, gregory.p.smith
2013-12-01 21:09:57neologixlinkissue19850 messages
2013-12-01 21:09:57neologixcreate