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 vinay.sajip
Recipients Kazutaka.Morita, vinay.sajip
Date 2012-06-25.15:06:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340636779.93.0.171189477395.issue15179@psf.upfronthosting.co.za>
In-reply-to
Content
Why should the socket need closing if the connect fails? This seems a flawed contract; either connect() should work (in which case the socket will need closing when it's finished with) or it should fail, not connect and not require a close call (as it isn't connected). Could this be a problem with eventlet? One could argue that the leak is actually in whatever implements socket.connect in this case (presumably eventlet).
History
Date User Action Args
2012-06-25 15:06:20vinay.sajipsetrecipients: + vinay.sajip, Kazutaka.Morita
2012-06-25 15:06:19vinay.sajipsetmessageid: <1340636779.93.0.171189477395.issue15179@psf.upfronthosting.co.za>
2012-06-25 15:06:19vinay.sajiplinkissue15179 messages
2012-06-25 15:06:19vinay.sajipcreate