Robert Buchholz added the comment:
It's been a year and the 3.4 alpha is approaching. What's the status of
upstream inclusion of this patch?
--
___
Python tracker
<http://bugs.python.o
Changes by Robert Buchholz :
--
nosy: +Robert.Buchholz
___
Python tracker
<http://bugs.python.org/issue13405>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Robert Buchholz :
--
nosy: +Robert.Buchholz
___
Python tracker
<http://bugs.python.org/issue14776>
___
___
Python-bugs-list mailing list
Unsubscribe:
Robert Buchholz added the comment:
almost... HTTPConnection is calling close() on the socket object, but
HTTPResponse still has an open file-like object from a previous makefile()
call. That object still has an internal reference to the socket
Robert Buchholz added the comment:
An example cannot be constructed using the standard python socket class. As you
point out, the response.will_close attribute is set correctly: The client is
supposed to close to connect after completion of the request (as does the
server). However, when the
New submission from Robert Buchholz :
Calling getresponse() on an httplib.HTTPConnection object returns a response
object. Internally, the self.sock is handed over to the HTTPResponse object
which transforms it into a file-like object. The response object is returned to
the caller. If one
