Message296571
If I use the Python 64-bit 2.7.13 Windows installer and install to C:\Program Files\Python27, then the Scripts folder doesn't get created and pip doesn't get installed. If I uninstall Python and reinstall it to C:\Python27, C:\Programs\Python27, or "C:\Path with spaces\Python27", then the Scripts folder is created and pip works correctly. If I install Python 2.7.12 using https://www.python.org/ftp/python/2.7.12/python-2.7.12.amd64.msi or Python 3.6.1 using https://www.python.org/ftp/python/3.6.1/python-3.6.1-amd64.exe, then I don't experience this issue. This issue does happen if I install to C:\PROGRA~1\Python27, which is the 8.3 filename equivalent of C:\Program Files\Python27. I've seen this on a handful of Windows 10 computers so far. I haven't tried other versions of Windows or the 32-bit installers.
Steps to reproduce:
- Download the Python installer from https://www.python.org/ftp/python/2.7.13/python-2.7.13.amd64.msi and run it.
- Select "Install for all users" and click Next.
- Enter C:\Program Files\Python27 as the installation folder and click Next.
- Click on "Register Extensions" and select "Entire feature will be unavailable". (I don't know if this step is required, but it's what I've been doing to test.) Click Next.
- Click Yes at the UAC prompt.
- Wait for installation to finish.
Expected results:
The "C:\Program Files\Python27\Scripts" and "C:\Program Files\Python27\Lib\site-packages\pip" folders should get created during the installation.
Actual results:
Neither of the folders exist. |
|
Date |
User |
Action |
Args |
2017-06-21 17:59:07 | KevKeating | set | recipients:
+ KevKeating, paul.moore, tim.golden, zach.ware, steve.dower |
2017-06-21 17:59:07 | KevKeating | set | messageid: <1498067947.84.0.203482425844.issue30725@psf.upfronthosting.co.za> |
2017-06-21 17:59:07 | KevKeating | link | issue30725 messages |
2017-06-21 17:59:07 | KevKeating | create | |
|