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 Chris Brennan
Recipients BreamoreBoy, Chris Brennan, DieInSente, dstufft, loewis, piotr.dobrogost, python-dev, steve.dower, tim.golden, venza, zach.ware
Date 2015-08-07.16:22:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1438964557.02.0.398790565565.issue22028@psf.upfronthosting.co.za>
In-reply-to
Content
This bug appears (for me) when I use longer install paths, both in the GUI installer and doing a silent install via msiexec. The paths I've used so far are these:

E:\langs\Python\x32\27
E:\langs\Python\x32\34
E:\langs\Python\x64\27
E:\langs\Python\x64\34

E:\Python\x32\27
E:\Python\x32\34
E:\Python\x64\27
E:\Python\x64\34

Both of these paths fail to install when pip is called. If I install to a single-level directory, the install works fine (doesn't matter what drive I use either....)
History
Date User Action Args
2015-08-07 16:22:37Chris Brennansetrecipients: + Chris Brennan, loewis, tim.golden, BreamoreBoy, python-dev, piotr.dobrogost, zach.ware, steve.dower, dstufft, DieInSente, venza
2015-08-07 16:22:37Chris Brennansetmessageid: <1438964557.02.0.398790565565.issue22028@psf.upfronthosting.co.za>
2015-08-07 16:22:36Chris Brennanlinkissue22028 messages
2015-08-07 16:22:36Chris Brennancreate