Message 58378 - 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	janssen
Recipients	christian.heimes, gvanrossum, janssen
Date	2007-12-10.22:37:46
SpamBayes Score	0.12792069
Marked as misclassified	No
Message-id	<1197326266.55.0.325304703864.issue1469@psf.upfronthosting.co.za>
In-reply-to

Content
So, what's the final status of __del__ in py3K? The other bit of leak is due to _real_close() not being called when a socket is dropped on the floor (say, you try to connect, fail, and raise the exception back to the caller, without ever explicitly calling close() on the opened socket). It looks like the __del__ method in SSLSocket isn't being called.

So, what's the final status of __del__ in py3K?  The other bit of leak
is due to _real_close() not being called when a socket is dropped on the
floor (say, you try to connect, fail, and raise the exception back to
the caller, without ever explicitly calling close() on the opened
socket).  It looks like the __del__ method in SSLSocket isn't being called.

History
Date	User	Action	Args
2007-12-10 22:37:46	janssen	set	spambayes_score: 0.127921 -> 0.12792069 recipients: + janssen, gvanrossum, christian.heimes
2007-12-10 22:37:46	janssen	set	spambayes_score: 0.127921 -> 0.127921 messageid: <1197326266.55.0.325304703864.issue1469@psf.upfronthosting.co.za>
2007-12-10 22:37:46	janssen	link	issue1469 messages
2007-12-10 22:37:46	janssen	create