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, barry, benjamin.peterson, cameron, dstufft, ethan.furman, larry, martin.panter, ned.deily, nikratio, orsenthil, python-dev
Date 2014-05-17.02:09:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1400292545.67.0.252286575158.issue7776@psf.upfronthosting.co.za>
In-reply-to
Content
Well you're the RM Larry :) I'll do whatever you think is best. I would greatly prefer it if the pip shipped with CPython 3.4.1 wasn't broken with proxies. I think the choices are

1) Ship it with the new pip, I can give a delta of the differences if that is helpful.
2) Roll back the patch that broke the behavior
3) Ship with broken pip + proxy behavior

Whichever you think is the better option is fine with me.
History
Date User Action Args
2014-05-17 02:09:05dstufftsetrecipients: + dstufft, barry, orsenthil, larry, benjamin.peterson, ned.deily, cameron, nikratio, ethan.furman, python-dev, martin.panter, Cybjit
2014-05-17 02:09:05dstufftsetmessageid: <1400292545.67.0.252286575158.issue7776@psf.upfronthosting.co.za>
2014-05-17 02:09:05dstufftlinkissue7776 messages
2014-05-17 02:09:05dstufftcreate