Christian Heimes <li...@cheimes.de> added the comment:
It looks like your code is treating a SSLSocket like an ordinary Kernel socket. SSLSocket are implemented in user space and behave differently. https://docs.python.org/3/library/ssl.html#ssl-nonblocking explains some of the aspects of non-blocking I/O for TLS connections. For non-blocking I/O it is generally easier to use sans-I/O approach and make use of MemoryBIO https://docs.python.org/3/library/ssl.html#memory-bio-support instead of SSLSocket. 3.6 and 3.7 only receive security updates and are out of scope anyway. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue43622> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
