Message 91409 - 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	gregory.p.smith
Recipients	gregory.p.smith, jorend, loewis, orenti, rhettg, sobomax
Date	2009-08-07.18:05:47
SpamBayes Score	0.00025285967
Marked as misclassified	No
Message-id	<1249668348.78.0.137341974318.issue1628205@psf.upfronthosting.co.za>
In-reply-to

Content
realistically, file objects (Objects/fileobject.c) never raise EINTR as they use the C library fread/fwrite/fclose underneath. Why should a socket based file object every be allowed to raise EINTR rather than handling it internally? IMHO people should only expect to handle EINTR when doing socket.send/recv or os.read/write/close, not using a file-like object.

realistically, file objects (Objects/fileobject.c) never raise EINTR as 
they use the C library fread/fwrite/fclose underneath.  Why should a 
socket based file object every be allowed to raise EINTR rather than 
handling it internally?

IMHO people should only expect to handle EINTR when doing 
socket.send/recv or os.read/write/close, not using a file-like object.

History
Date	User	Action	Args
2009-08-07 18:05:49	gregory.p.smith	set	recipients: + gregory.p.smith, loewis, jorend, orenti, sobomax, rhettg
2009-08-07 18:05:48	gregory.p.smith	set	messageid: <1249668348.78.0.137341974318.issue1628205@psf.upfronthosting.co.za>
2009-08-07 18:05:47	gregory.p.smith	link	issue1628205 messages
2009-08-07 18:05:47	gregory.p.smith	create