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 jhylton
Recipients jhylton, kristjan.jonsson, vstinner
Date 2008-11-29.01:52:24
SpamBayes Score 7.374338e-09
Marked as misclassified No
Message-id <>
In-reply-to <>
I did the simple part of the patch, where the request and headers are
sent at the same time.  The applied patch didn't pass the test suite,
and I want to think about the buffering change a bit more.  It's
definitely tricky.


On Fri, Nov 28, 2008 at 5:53 AM, Kristján Valur Jónsson
<> wrote:
> Kristján Valur Jónsson <> added the comment:
> Guido pointed out the problem with _fileobject.readline() being
> followed by socket.recv() if readline uses read buffering.
> was attempting to directly use the underlying socket,
> although in actual fact it never did, (since HTTPConnectio had closed
> it when it returned the response from getresponse()) Never the less, it
> is prudent to make sure that we don't attempt this.
> There really should be no need to use the socket directly, a buffered
> read() call is just as efficient.
> Added file:
> _______________________________________
> Python tracker <>
> <>
> _______________________________________
> _______________________________________________
> Python-bugs-list mailing list
> Unsubscribe:
Date User Action Args
2008-11-29 01:52:26jhyltonsetrecipients: + jhylton, kristjan.jonsson, vstinner
2008-11-29 01:52:25jhyltonlinkissue4336 messages
2008-11-29 01:52:24jhyltoncreate