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
Date 2010-09-16.11:47:38
SpamBayes Score 0.00420621
Marked as misclassified No
Message-id <1284637660.64.0.468391575207.issue9867@psf.upfronthosting.co.za>
In-reply-to
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:

mitsuhiko@nausicaa:~$ ruby -e 'puts $stdin.read.inspect'
^Z
[1]+  Stopped
mitsuhiko@nausicaa:~$ fg
ruby -e 'puts $stdin.read.inspect'
test
"test\n"



So does perl:

mitsuhiko@nausicaa:~$ perl -e 'chomp($x = <STDIN>); print $x'
^Z
[1]+  Stopped
mitsuhiko@nausicaa:~$ fg
perl -e 'chomp($x = <STDIN>); print $x'
test
test
History
Date User Action Args
2010-09-16 11:47:40aronachersetrecipients: + aronacher, loewis, ned.deily
2010-09-16 11:47:40aronachersetmessageid: <1284637660.64.0.468391575207.issue9867@psf.upfronthosting.co.za>
2010-09-16 11:47:39aronacherlinkissue9867 messages
2010-09-16 11:47:38aronachercreate