Guido van Rossum added the comment: > 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. __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1469> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
