➜

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 martin.panter
Recipients barry, martin.panter, orsenthil, serhiy.storchaka
Date 2013-12-20.03:03:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1387508602.51.0.459801271158.issue19524@psf.upfronthosting.co.za>
In-reply-to
Content 
How is it safer to manually set “h.sock._closed”? Playing with the internals of HTTPConnection is one thing, but playing with the internals of the socket object as well does not seem necessary.

Also the ResourceWarning is warning that the socket and connection were closed by the garbage collector at some arbitrary point. I don’t think a new __del__() method is going to help. Sorry to be so negative :)

Related issues:
Issue 18144: FD leak in urllib2 (probably an exact dupe)
Issue 11563: test_urllibnet is triggering a ResourceWarning (bug closed, but real issue was only side-stepped IMO)
History
Date User Action Args
2013-12-20 03:03:22martin.pantersetrecipients: + martin.panter, barry, orsenthil, serhiy.storchaka
2013-12-20 03:03:22martin.pantersetmessageid: <1387508602.51.0.459801271158.issue19524@psf.upfronthosting.co.za>
2013-12-20 03:03:22martin.panterlinkissue19524 messages
2013-12-20 03:03:21martin.pantercreate