Guido van Rossum <gu...@python.org> added the comment: IIUC the problem is that a read() syscall on the pty after the other end has been closed raises an error instead of reading 0 bytes? Isn't that a bug in the pty implementation? For lots of devices (e.g. sockets, pipes) a short non-empty read just means that you have to call read() again to get more data -- it does not mean EOF.
_______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5380> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
