Author gvanrossum
Recipients gregory.p.smith, gvanrossum, neologix, vstinner
Date 2013-12-02.16:54:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386003267.18.0.726296933745.issue19850@psf.upfronthosting.co.za>
In-reply-to
Content
I have a question. Is there actually any need for this with asyncio? The selector already handles EINTR, and all the I/O done by asyncio's transports already handles it too (there are "except (BlockingIOError, InterruptedError)" clauses all over the place).

Any *other* I/O syscalls (unless a program violates the asyncio rules against doing your own blocking I/O) would either be disk file I/O, which IIUC cannot elicit EINTR, or run in a separate thread, where presumably it wouldn't be interrupted by a signal handler, since SIGCHLD is delivered to the main thread.  (It's actually the last part I am not 100% sure of.)
History
Date User Action Args
2013-12-02 16:54:27gvanrossumsetrecipients: + gvanrossum, gregory.p.smith, vstinner, neologix
2013-12-02 16:54:27gvanrossumsetmessageid: <1386003267.18.0.726296933745.issue19850@psf.upfronthosting.co.za>
2013-12-02 16:54:27gvanrossumlinkissue19850 messages
2013-12-02 16:54:26gvanrossumcreate