Message116539
> 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 |
|
Date |
User |
Action |
Args |
2010-09-16 12:36:50 | aronacher | set | recipients:
+ aronacher, loewis, ronaldoussoren, ned.deily |
2010-09-16 12:36:50 | aronacher | set | messageid: <1284640610.68.0.456949284144.issue9867@psf.upfronthosting.co.za> |
2010-09-16 12:36:48 | aronacher | link | issue9867 messages |
2010-09-16 12:36:47 | aronacher | create | |
|