Guido van Rossum added the comment: So maybe we should just close this as won't fix. Whoever wants to use the master end of a pty had better be prepared for that IOError.
On Thursday, October 8, 2015, Martin Panter <rep...@bugs.python.org> wrote: > > Martin Panter added the comment: > > My biggest worry about the patch is that it looks like it will mask other > EIO errors from normal terminals (e.g. perhaps reading from a slave or a > real serial port can also produce an EIO error that does not mean EOF). > Another option may be to add a specialized pseudo terminal master wrapper > class that does the right thing on Linux. But I’m not a pseudo terminal > expert and don’t really have a strong view about this. > > I agree that the “pty” module is rather limited, although the > documentation does say pty.openpty() is more portable than os.openpty(). > Maybe if Python used posix_openpt(), portability would be less of a problem? > > ---------- > > _______________________________________ > Python tracker <rep...@bugs.python.org <javascript:;>> > <http://bugs.python.org/issue5380> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5380> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com