➜

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 dabeaz
Recipients amaury.forgeotdarc, beazley, dabeaz, gregory.p.smith, loewis, ned.deily, pitrou, rosslagerwall, roysmith
Date 2011-01-14.20:00:50
SpamBayes Score 8.9347544e-05
Marked as misclassified No
Message-id <1295035254.36.0.429500193171.issue7322@psf.upfronthosting.co.za>
In-reply-to
Content 
Just wanted to say that I agree it's nonsense to continue reading on a socket that timed out (I'm not even sure what I might have been thinking when I first submitted this bug other than just experimenting with edge cases of the socket interface).    It's still probably good to precisely specify what the behavior is in any case.
History
Date User Action Args
2011-01-14 20:00:54dabeazsetrecipients: + dabeaz, loewis, beazley, gregory.p.smith, amaury.forgeotdarc, roysmith, pitrou, ned.deily, rosslagerwall
2011-01-14 20:00:54dabeazsetmessageid: <1295035254.36.0.429500193171.issue7322@psf.upfronthosting.co.za>
2011-01-14 20:00:50dabeazlinkissue7322 messages
2011-01-14 20:00:50dabeazcreate