[issue5882] __repr__ is ignored when formatting exceptions

2009-04-29 Thread Jonathan Ellis
Changes by Jonathan Ellis : -- versions: +Python 3.0 ___ Python tracker <http://bugs.python.org/issue5882> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue5882] __repr__ is ignored when formatting exceptions

2009-04-29 Thread Jonathan Ellis
New submission from Jonathan Ellis : The docs say that "If a class defines __repr__() but not __str__(), then __repr__() is also used when an “informal” string representation of instances of that class is required." but, repr is ignored: >>> class E(Exception): ...

[issue1291446] SSLObject breaks read semantics

2008-09-05 Thread Jonathan Ellis
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

2008-09-04 Thread Jonathan Ellis
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, otherwis

[issue1291446] SSLObject breaks read semantics

2008-09-03 Thread Jonathan Ellis
Jonathan Ellis <[EMAIL PROTECTED]> added the comment: s/raw socket read/raw socket recv/ ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1291446] SSLObject breaks read semantics

2008-09-03 Thread Jonathan Ellis
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.