Message 129481 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	giampaolo.rodola, pitrou, segfaulthunter
Date	2011-02-26.00:56:52
SpamBayes Score	6.0521797e-06
Marked as misclassified	No
Message-id	<1298681816.23.0.62495161994.issue11326@psf.upfronthosting.co.za>
In-reply-to

Content
> The select call after the connect_ex waits until the connection is > done, for the first write event is fired then, so the socket is > connected afterwards. You are right. Here is a patch for py3k implementing connect_ex() and solving the issue with the missing "_sslobj" attribute. It makes your script run fine. (ideally I should add some tests to the patch, at least for connect_ex)

> The select call after the connect_ex waits until the connection is
> done, for the first write event is fired then, so the socket is
> connected afterwards.

You are right. Here is a patch for py3k implementing connect_ex() and solving the issue with the missing "_sslobj" attribute. It makes your script run fine.

(ideally I should add some tests to the patch, at least for connect_ex)

History
Date	User	Action	Args
2011-02-26 00:56:56	pitrou	set	recipients: + pitrou, giampaolo.rodola, segfaulthunter
2011-02-26 00:56:56	pitrou	set	messageid: <1298681816.23.0.62495161994.issue11326@psf.upfronthosting.co.za>
2011-02-26 00:56:53	pitrou	link	issue11326 messages
2011-02-26 00:56:53	pitrou	create