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 demian.brecht
Recipients berker.peksag, demian.brecht, martin.panter, orsenthil, r.david.murray
Date 2015-10-08.19:37:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yeah, agreed that it should be opt-in, at least until a major release.

I've run into a couple cases where higher level libraries use http.client (or httplib) directly, but don't expose the client directly (not that they should anyways). Because of that, there are higher level libraries that simply /can't/ support http_proxy environment variable because they didn't use a higher level abstraction.

Given http.client /does/ implement everything required to support this, I can't see it impacting the architecture in any negative way.
Date User Action Args
2015-10-08 19:37:31demian.brechtsetrecipients: + demian.brecht, orsenthil, r.david.murray, berker.peksag, martin.panter
2015-10-08 19:37:31demian.brechtsetmessageid: <>
2015-10-08 19:37:31demian.brechtlinkissue24177 messages
2015-10-08 19:37:31demian.brechtcreate