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 aronacher
Recipients aronacher, loewis, ned.deily, ronaldoussoren
Date 2010-09-16.12:36:47
SpamBayes Score 0.0016857253
Marked as misclassified No
Message-id <1284640610.68.0.456949284144.issue9867@psf.upfronthosting.co.za>
In-reply-to
Content
> Wouldn't retrying on EINTR cause havoc when you try to interrupt a process?

All your C applications are doing it, why should Python cause havok there?  Check the POSIX specification on that if you don't trust me.

> That is: what would happen with the proposed patch when a python script
> does a read that takes a very long time and the user tries to interrupt 
> the script (by using Ctrl+C to send a SIGTERM)?
EINTR is only returned if nothing was read so far and the call was interrupted in case of fread.

Here a quick explanation from the GNU's libc manual:
http://www.gnu.org/s/libc/manual/html_node/Interrupted-Primitives.html
History
Date User Action Args
2010-09-16 12:36:50aronachersetrecipients: + aronacher, loewis, ronaldoussoren, ned.deily
2010-09-16 12:36:50aronachersetmessageid: <1284640610.68.0.456949284144.issue9867@psf.upfronthosting.co.za>
2010-09-16 12:36:48aronacherlinkissue9867 messages
2010-09-16 12:36:47aronachercreate