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 giampaolo.rodola, irmen, loewis, martin.panter, pitrou, vstinner
Date 2015-11-10.02:44:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1447123461.18.0.273940764641.issue1103213@psf.upfronthosting.co.za>
In-reply-to
Content
I can’t say I’ve often wanted this kind of method for socket objects. I guess this would treat a zero-length message (e.g. UDP datagram) as end-of-stream. Maybe it would be more useful as a general function or method for RawIOBase (maybe also BufferedIOBase) streams.

As for the exception, I have used the existing EOFError in the past for similar purposes. After all, an unexpected EOF error at a low level often means an incomplete or truncated data error at a higher level.
History
Date User Action Args
2015-11-10 02:44:21martin.pantersetrecipients: + martin.panter, loewis, irmen, pitrou, vstinner, giampaolo.rodola
2015-11-10 02:44:21martin.pantersetmessageid: <1447123461.18.0.273940764641.issue1103213@psf.upfronthosting.co.za>
2015-11-10 02:44:21martin.panterlinkissue1103213 messages
2015-11-10 02:44:19martin.pantercreate