Armin Ronacher <armin.ronac...@active-4.com> added the comment: > 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 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9867> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
