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 loewis
Recipients aronacher, loewis, ned.deily
Date 2010-09-16.12:03:36
SpamBayes Score 0.011253131
Marked as misclassified No
Message-id <4C920796.30409@v.loewis.de>
In-reply-to <1284637660.64.0.468391575207.issue9867@psf.upfronthosting.co.za>
Content
> One could argue of course that every user of Python should handle
> EINTR, but that's something I think should be solved in the IO
> library because very few people know that one is supposed to restart
> syscalls on EINTR on POSIX systems.
>
> Ruby for instance handles EINTR properly:

Hmm. So under what conditions should it continue, and under what 
conditions should it raise an exception (when errno is EINTR)?
History
Date User Action Args
2010-09-16 12:03:39loewissetrecipients: + loewis, ned.deily, aronacher
2010-09-16 12:03:37loewislinkissue9867 messages
2010-09-16 12:03:36loewiscreate