Stefan Krah added the comment: I had a similar issue with ucspi-ssl that was fixed by following the O'Reilly book's recommendations w.r.t WANT_READ/WANT_WRITE with non-blocking sockets to the letter.
The recommendations are quite complex since apparently WANT_READ/WANT_WRITE mean different things depending on whether they occur *during a read* or *during a write*. I haven't used Python's SSL module much: Since those flags are exposed on the Python level, are users supposed to take care of the above issues themselves for non-blocking sockets? ---------- nosy: +skrah _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22499> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
