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 martin.panter
Recipients Arfrever, amaury.forgeotdarc, exarkun, gvanrossum, marcio, marduk, martin.panter, ocean-city, pitrou, xdegaye, zmedico
Date 2015-10-09.05:07:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444367253.52.0.144884590146.issue5380@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2015-10-09 05:07:33martin.pantersetrecipients: + martin.panter, gvanrossum, exarkun, amaury.forgeotdarc, pitrou, ocean-city, Arfrever, marduk, zmedico, marcio, xdegaye
2015-10-09 05:07:33martin.pantersetmessageid: <1444367253.52.0.144884590146.issue5380@psf.upfronthosting.co.za>
2015-10-09 05:07:33martin.panterlinkissue5380 messages
2015-10-09 05:07:33martin.pantercreate