STINNER Victor added the comment: Here is a patch to fix the issue: recompute the timeout.
It's unclear to me if we should reset the timeout after each successful read/write, or if the timeout is "global" (total duration of the ssl method). I asked the question on the python-dev mailing list. https://mail.python.org/pipermail/python-dev/2015-April/139001.html My patch uses a global timeout (never reset the timeout), whereas socket.sendall() resets the timeout at each send() success. ---------- Added file: http://bugs.python.org/file38816/ssl_timeout.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23853> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
