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 amaury.forgeotdarc, christian.heimes, gvanrossum, janssen
Date 2007-12-11.01:26:54
SpamBayes Score 0.3657769
Marked as misclassified No
Message-id <1197336415.57.0.0492151333629.issue1469@psf.upfronthosting.co.za>
In-reply-to
Content
I think Christian analysis is right, in that it takes a bit of GC
support, but not perhaps in the specifics of his approach.  I've done
two things to fix this:

1)  Put _real_close() back in socket.py, and then override it in
ssl.SSLSocket to release the SSLContext, and

2)  Change the pointer to the SSLSocket in _ssl.c to a weakref.

Now SSLSockets get cleaned up properly by the GC system.

One question: _real_close() is what Java calls a "protected" method.  Do
we have any way to mark this with annotations or metaclass stuff?
History
Date User Action Args
2007-12-11 01:26:55janssensetspambayes_score: 0.365777 -> 0.3657769
recipients: + janssen, gvanrossum, amaury.forgeotdarc, christian.heimes
2007-12-11 01:26:55janssensetspambayes_score: 0.365777 -> 0.365777
messageid: <1197336415.57.0.0492151333629.issue1469@psf.upfronthosting.co.za>
2007-12-11 01:26:55janssenlinkissue1469 messages
2007-12-11 01:26:54janssencreate