Message 82861 - Python tracker

➜

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	amaury.forgeotdarc, gvanrossum, ocean-city, pitrou, zmedico
Date	2009-02-27.19:27:01
SpamBayes Score	1.0927975e-07
Marked as misclassified	No
Message-id	<1235762823.6.0.000504273092433.issue5380@psf.upfronthosting.co.za>
In-reply-to

Content
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.

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.

History
Date	User	Action	Args
2009-02-27 19:27:03	gvanrossum	set	recipients: + gvanrossum, amaury.forgeotdarc, pitrou, ocean-city, zmedico
2009-02-27 19:27:03	gvanrossum	set	messageid: <1235762823.6.0.000504273092433.issue5380@psf.upfronthosting.co.za>
2009-02-27 19:27:01	gvanrossum	link	issue5380 messages
2009-02-27 19:27:01	gvanrossum	create