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 gvanrossum
Recipients Arfrever, amaury.forgeotdarc, exarkun, gvanrossum, marcio, marduk, martin.panter, ocean-city, pitrou, xdegaye, zmedico
Date 2015-10-09.05:18:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJ+jsLt6u80wYz1S+N6Ld4=PXbR6j4KJLdnUJSNgGtGfCw@mail.gmail.com>
In-reply-to <1444367253.52.0.144884590146.issue5380@psf.upfronthosting.co.za>
Content
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 <report@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 <report@bugs.python.org <javascript:;>>
> <http://bugs.python.org/issue5380>
> _______________________________________
>
History
Date User Action Args
2015-10-09 05:18:33gvanrossumsetrecipients: + gvanrossum, exarkun, amaury.forgeotdarc, pitrou, ocean-city, Arfrever, marduk, zmedico, marcio, xdegaye, martin.panter
2015-10-09 05:18:33gvanrossumlinkissue5380 messages
2015-10-09 05:18:33gvanrossumcreate