[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Cyril report at bugs.python.org
Fri Mar 26 19:47:41 CET 2010


Cyril <cbay at excellency.fr> added the comment:

pitrou: that's debatable, since the Python programmer has no control over memory pointers. As I said, I have a cStringIO buffer, and two consecutive calls to buffer.getvalue() yield different objects. What can I do about it? I think it's a rather sane scenario, and I don't feel I'm doing anything wrong.

If you think the programmer should be alerted about it, however, then we should at least say it explicitely in the documentation and probably return an explicit Python error. I had to google quite a bit before finding out what this error meant:

error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8240>
_______________________________________


More information about the Python-bugs-list mailing list