➜

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 joshuaellinger
Recipients eryksun, joshuaellinger, steve.dower, tim.golden, zach.ware
Date 2014-12-27.22:04:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <9B7FBDF2-7291-4965-BFCA-3D7C6B349C72@exemplartech.com>
In-reply-to <1419695347.82.0.292727249821.issue23121@psf.upfronthosting.co.za>
Content 
Having pip not work after a straight install to the normal place you'd install it on windows can't be a feature.

Even after I changed the .exe, pip itself breaks on the same problem.  Basically, you can't install python to
the normal place on windows until this is fixed.

Josh

On Dec 27, 2014, at 9:49 AM, Steve Dower <report@bugs.python.org> wrote:

> 
> Steve Dower added the comment:
> 
> I've previously reported this issue against setuptools (which generates the executable) and apparently they consider it a "feature". I don't have the link handy from my phone, but if you find the issue on bitbucket you can help attract some more attention to this.
> 
> ----------
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue23121>
> _______________________________________
History
Date User Action Args
2014-12-27 22:04:53joshuaellingersetrecipients: + joshuaellinger, tim.golden, zach.ware, eryksun, steve.dower
2014-12-27 22:04:53joshuaellingerlinkissue23121 messages
2014-12-27 22:04:52joshuaellingercreate