➜

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 PoltoS
Recipients PoltoS, TTT, amaury.forgeotdarc, dandrzejewski, eric.smith, giampaolo.rodola, orsenthil, pitrou, r.david.murray
Date 2010-10-16.21:24:49
SpamBayes Score 3.7039996e-09
Marked as misclassified No
Message-id <1287264291.67.0.753158338829.issue10127@psf.upfronthosting.co.za>
In-reply-to
Content 
After some investigations it seems that a dup() is called in ssl wrap_socket(), so on sock.close() the socket is not really closed, since there is still one more reference (file descriptor) in the kernel's tcp/ip stack. Can someone confirm this?

Have not done this, but it is possible to check my supposition using linux lsof command before and after .close().
History
Date User Action Args
2010-10-16 21:24:51PoltoSsetrecipients: + PoltoS, amaury.forgeotdarc, orsenthil, pitrou, eric.smith, giampaolo.rodola, r.david.murray, dandrzejewski, TTT
2010-10-16 21:24:51PoltoSsetmessageid: <1287264291.67.0.753158338829.issue10127@psf.upfronthosting.co.za>
2010-10-16 21:24:50PoltoSlinkissue10127 messages
2010-10-16 21:24:49PoltoScreate