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 janssen
Recipients ellisj, janssen
Date 2008-09-04.20:03:21
SpamBayes Score 5.4725984e-07
Marked as misclassified No
Message-id <1220558602.61.0.858885949857.issue1291446@psf.upfronthosting.co.za>
In-reply-to
Content
The way I read the documentation, file.read() (and that's what we're
talking about) is still not guaranteed to read all the bytes of the
file.  But, you're right, that is the accepted semantics.  So the
documentation should change, too.

However, the "read" method on an SSLSocket, which is not a file()
subclass, is *not* guaranteed to return N bytes, it's guaranteed to
return at most N bytes.  Call "makefile" on SSLSocket if you need a
file-like object.
History
Date User Action Args
2008-09-04 20:03:22janssensetrecipients: + janssen, ellisj
2008-09-04 20:03:22janssensetmessageid: <1220558602.61.0.858885949857.issue1291446@psf.upfronthosting.co.za>
2008-09-04 20:03:22janssenlinkissue1291446 messages
2008-09-04 20:03:21janssencreate