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 r.david.murray
Recipients brokenenglish, r.david.murray
Date 2017-01-23.19:44:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485200681.49.0.645997038968.issue29353@psf.upfronthosting.co.za>
In-reply-to
Content
IMO http *should* be using headersonly=True, so while I haven't looked into this issue the solution seems plausible to me.  I'm not entirely sure why it is considered a backward-compatibility hack, but I don't see any likelyhood that the headersonly API will go way.
History
Date User Action Args
2017-01-23 19:44:41r.david.murraysetrecipients: + r.david.murray, brokenenglish
2017-01-23 19:44:41r.david.murraysetmessageid: <1485200681.49.0.645997038968.issue29353@psf.upfronthosting.co.za>
2017-01-23 19:44:41r.david.murraylinkissue29353 messages
2017-01-23 19:44:41r.david.murraycreate