[issue18144] FD leak in urllib2

Changes by Serhiy Storchaka : -- resolution: -> duplicate status: open -> closed superseder: -> test_urllib2net is triggering a ResourceWarning ___ Python tracker ___ _

[issue18144] FD leak in urllib2

Claudio Freire added the comment: Yes, seems it does. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue18144] FD leak in urllib2

Martin Panter added the comment: Does the fix for Issue 12692 work for you? Namely this revision . It was backported to C Python 3.3.4 as I understand. -- ___ Python tracker

[issue18144] FD leak in urllib2

Claudio Freire added the comment: I can confirm the issue is in urllib's open: it fails to close() the HTTP connection, leaving it to the GC to do it. If addinfourl (and friends) is altered to carry a reference to the HTTP connection and close it on close(), the leak is fixed. I have a patch

[issue18144] FD leak in urllib2

Changes by Serhiy Storchaka : -- nosy: +pitrou, serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue18144] FD leak in urllib2

Martin Panter added the comment: Confirmed that this happens when the server sends a chunked response, or sends a Content-Length header, but not when the server just sends “Connection: close”. So this looks like the same as Issue 19524, and my patch for that seems to fix the issue here. Pytho

[issue18144] FD leak in urllib2

Changes by Alexander Boyd : -- nosy: +javawizard ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue18144] FD leak in urllib2

New submission from Claudio Freire: While other issues already exist about this problem, this particular case is unlike other issues, and I didn't think it a good idea to merge with those. Under some very specific circumstances (sending a POST request with more data than an unknown threshold),