Author janssen
Recipients chris.stawarz, giampaolo.rodola, jafo, janssen, jcea
Date 2008-05-16.00:21:49
SpamBayes Score 0.00371121
Marked as misclassified No
Message-id <>
In-reply-to <>
Here's what's in the 3.0 docs:

The parameter do_handshake_on_connect specifies whether to do the SSL
handshake automatically after doing a socket.connect(), or whether the
application program will call it explicitly, by invoking the
gives the program control over the blocking behavior of the
socket I/O involved in the handshake.

Look at test.test_ssl.testNonBlockingHandshake() in 3.0alpha or in the PyPI
module.  I'm still working on 2.6.


On Thu, May 15, 2008 at 3:56 PM, Jesús Cea Avión <>

> Jesús Cea Avión <> added the comment:
> I'm hitting this issue aswell. How is going?.
> I'm creating a socket with a, let say, 5 seconds timeout. The timeout
> works fine before the "wrap_socket()", and after it. But the timeout
> doesn't work WHILE in the "wrap_socket()" method call.
> What can I do?.
> If I need to call "do_handshake()" myself, working with
> SSL_ERROR_WANT_READ/WRITE, I think this *needs* to be documented somewhere.
> That is, any difference between "normal" sockets and "ssl" sockets need
> to be documented in docs. Explicitly.
> My opinion, of course :).
> __________________________________
> Tracker <>
> <>
> __________________________________
File name Uploaded
unnamed janssen, 2008-05-16.00:21:46
Date User Action Args
2008-05-16 00:22:17janssensetspambayes_score: 0.00371121 -> 0.00371121
recipients: + janssen, jafo, jcea, giampaolo.rodola, chris.stawarz
2008-05-16 00:21:49janssenlinkissue1251 messages
2008-05-16 00:21:49janssencreate