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 dstufft
Recipients Cybjit, benjamin.peterson, cameron, dstufft, ethan.furman, larry, martin.panter, ned.deily, nikratio, orsenthil, python-dev
Date 2014-05-11.21:14:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1399842867.71.0.933541392224.issue7776@psf.upfronthosting.co.za>
In-reply-to
Content
This is going to break existing versions of urllib3 (and thus requests and thus pip) when using verified TLS + a proxy, however future versions can work around it and a fix is being looked at right now. Once it's fixed there it can propagate to requests and then to pip.

Urllib3 issue is here https://github.com/shazow/urllib3/issues/385

As far as what CPython should do. I personally don't think 3.4.1 should go out with this broken. That'll mean either getting a new pip out with the fix and bump the bundled version in CPython or revert this patch and wait till 3.5 (or 3.4.2 if you don't want to hold up 3.4.1).
History
Date User Action Args
2014-05-11 21:14:27dstufftsetrecipients: + dstufft, orsenthil, larry, benjamin.peterson, ned.deily, cameron, nikratio, ethan.furman, python-dev, martin.panter, Cybjit
2014-05-11 21:14:27dstufftsetmessageid: <1399842867.71.0.933541392224.issue7776@psf.upfronthosting.co.za>
2014-05-11 21:14:27dstufftlinkissue7776 messages
2014-05-11 21:14:27dstufftcreate