Message 58382 - 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	gvanrossum
Recipients	amaury.forgeotdarc, christian.heimes, gvanrossum, janssen
Date	2007-12-10.23:17:09
SpamBayes Score	0.11066286
Marked as misclassified	No
Message-id	<ca471dc20712101517g570f1c1cj1ff34a7f6280ff98@mail.gmail.com>
In-reply-to	<1197326266.55.0.325304703864.issue1469@psf.upfronthosting.co.za>

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. There are no current plans to change __del__ in Py3k.

> 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.

There are no current plans to change __del__ in Py3k.

History
Date	User	Action	Args
2007-12-10 23:17:09	gvanrossum	set	spambayes_score: 0.110663 -> 0.11066286 recipients: + gvanrossum, amaury.forgeotdarc, janssen, christian.heimes
2007-12-10 23:17:09	gvanrossum	link	issue1469 messages
2007-12-10 23:17:09	gvanrossum	create