[issue29586] Cannot run pip in fresh install of py 3.5.3

Steve Dower added the comment: This was caused by the UCRT not installing properly. These days, the UCRT is installed app-local for Win 8.1, and is already present on Win 10, so it can't happen anymore. -- resolution: -> fixed stage: -> resolved status: open -> closed

[issue29586] Cannot run pip in fresh install of py 3.5.3

Eryk Sun added the comment: This issue is similar to bpo-25117 in terms of the installer failing to run Python for post-installation tasks. The complication in this case is that a subsequent repair doesn't install pip. -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.5

[issue29586] Cannot run pip in fresh install of py 3.5.3

Adrian Chan added the comment: Ah, I'd forgotten about that. When I first tried to run python I got an error complaining about a missing api-ms-win-crt-runtime-l1-1.0.dll I installed the necessary VC redistributable and it solved that problem. So that's why I could successfully ensurepip

[issue29586] Cannot run pip in fresh install of py 3.5.3

Steve Dower added the comment: Depending on why the pip install failed, we may still have registered that it was installed. IIRC, we only trigger the install on a state change, which wouldn't happen in repair. That deserves its own bug (though maybe this one will suffice if we figure out the

[issue29586] Cannot run pip in fresh install of py 3.5.3

Eryk Sun added the comment: The original install failed with the status code STATUS_DLL_NOT_FOUND (0xC135), as reported in "Python 3.5.3 (32-bit)_20170217102132_008_pip_JustForMe.log": MSI (s) (88:D8) [10:22:59:574]: Executing op: ActionStart(Name=UpdatePip,,) MSI (s) (88:D8)

[issue29586] Cannot run pip in fresh install of py 3.5.3

Adrian Chan added the comment: Install logs attached. First set from initial install, second set from repair. -- Added file: http://bugs.python.org/file46645/py_install_logs.tar.gz ___ Python tracker

[issue29586] Cannot run pip in fresh install of py 3.5.3

Eryk Sun added the comment: If you have the 3.5 installation logs in your %TEMP% directory, please zip them up and attach them to this issue. -- ___ Python tracker

[issue29586] Cannot run pip in fresh install of py 3.5.3

Adrian Chan added the comment: It's all working fine now, thanks. If one of the installer/windows guys wants to dig more into why this didn't install properly I'm happy to run things in my environment as necessary. -- ___ Python tracker

[issue29586] Cannot run pip in fresh install of py 3.5.3

Eryk Sun added the comment: pip should be installed in site-packages, which for you is "C:\Python\Python35-32\Lib\site-packages". Try manually running ensurepip to make sure pip is installed: python -m ensurepip --verbose --upgrade --default-pip --

[issue29586] Cannot run pip in fresh install of py 3.5.3

Adrian Chan added the comment: Thanks, but I know how to drive a terminal ;) Your hunch was basically correct though. I ran again with `python -v -m pip` (see with_pip_dir.txt), and see that python is attempting to import pip from my user directory (C:\Users\amc2\pip). This is an empty

[issue29586] Cannot run pip in fresh install of py 3.5.3

Eryk Sun added the comment: That error looks like __init__.py[c] was left in "C:\python27\lib\site-packages\pip". Just to be sure, since I don't know what you did to clear the value, please run `set PYTHONPATH=` to clear the value for the current shell. Then try `python -m pip`. When you

[issue29586] Cannot run pip in fresh install of py 3.5.3

Adrian Chan added the comment: There is no traceback, that is the entirety of the output of the command. Python bin is C:\Python\Python35-32\python.exe PYTHONHOME is not set. PYTHONPATH is C:\python27\lib\site-packages\ I don't know why PYTHONPATH was set. I cleared it but it made no

[issue29586] Cannot run pip in fresh install of py 3.5.3

Eryk Sun added the comment: Please provide the complete traceback. Copy and paste it from the command prompt. Also, include the fully-qualified path for what "python" runs, e.g. run `where python` in the command prompt. Also, include the value of the environment variables PYTHONHOME and

[issue29586] Cannot run pip in fresh install of py 3.5.3

New submission from Adrian Chan: I uninstalled python 2.7 and 3.4, then performed a fresh install of 3.5.3. Running pip with `python -m pip` as per https://docs.python.org/3.5/installing gives the following error: C:\Python\Python35-32\python.exe: No module named pip.__main__; 'pip' is a