[issue1291446] SSLObject breaks read semantics

Jonathan Ellis <[EMAIL PROTECTED]> added the comment: Ah, great. I was wondering why you kept talking about SSLSocket instead of SSLObject. "New API in 2.6" is good enough for me. Thanks! ___ Python tracker <[EMAIL PROTECTED]>

[issue1291446] SSLObject breaks read semantics

Bill Janssen <[EMAIL PROTECTED]> added the comment: Ah, sorry. I was looking at the 2.6 documentation, not the 2.5 documentation. In 2.6 (which is what the new SSL code is for), documentation of socket.ssl has been removed entirely, along with the text that you cite, although the functionality

[issue1291446] SSLObject breaks read semantics

Jonathan Ellis <[EMAIL PROTECTED]> added the comment: Here is the exact SSLObject.read documentation from 2.5 (although the bug was filed against 2.4, and 2.6 will be out soon, the docs are the same): - read([n]) If n is provided, read n bytes from the SSL connection, otherwise read unt

[issue1291446] SSLObject breaks read semantics

Bill Janssen <[EMAIL PROTECTED]> added the comment: 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

[issue1291446] SSLObject breaks read semantics

Jonathan Ellis <[EMAIL PROTECTED]> added the comment: s/raw socket read/raw socket recv/ ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python

[issue1291446] SSLObject breaks read semantics

Jonathan Ellis <[EMAIL PROTECTED]> added the comment: This is incorrect. Perhaps you are thinking of a raw socket read; a _file-like-object_ read is supposed to return the amount of data requested, unless (a) the socket is in non-blocking mode, or (b) if EOF is reached first. Normal socket.m

[issue1291446] SSLObject breaks read semantics

Changes by Bill Janssen <[EMAIL PROTECTED]>: -- status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-lis

[issue1291446] SSLObject breaks read semantics

Bill Janssen <[EMAIL PROTECTED]> added the comment: I think I'm going to close this. file.read(N) is not guaranteed to return N bytes, it's guaranteed to return at most N bytes. -- resolution: -> rejected ___ Python tracker <[EMAIL PROTECTED]>

[issue1291446] SSLObject breaks read semantics

Changes by Bill Janssen <[EMAIL PROTECTED]>: -- assignee: -> janssen nosy: +janssen ___ Python tracker <[EMAIL PROTECTED]> ___ ___ P