pip/easy_install failure: failed to create process
Question:
After following this article: How do I install pip on Windows? on my Windows system using Enthought Canopy 64 Bit system, I cannot get pip or easy_install to work due to error:
pip install requests
failed to create process
I tried re-installing setuptools, running cmd prompt as admin without any effect.
Answers:
When I encountered this, it was because I’d manually renamed the directory python was in. This meant that both setuptools and pip had to be reinstalled. Or, I had to manually rename the python directory to what it had been previously.
If you intentionally want to rename the folder where python.exe resides, you should also modify all python files in the Scripts folder. So a third solution would be to modify the python files as well: the first line in pip-2.7-script.py originally contain:
#!C:OriginalPythonDirpython.exe
Modifying this path to the new Python folder fixes the problem.
(P.S. Unfortunately I cannot yet reply to answers, so I’ll reply as a new answer because I thought it could be useful for other people as well).
I had installed Anaconda and so I still had C:Python27 along with C:Anaconda in my path. When I removed C:Python27 and all subfolders I was able to use pip again.
I just use python in the command shell on Windows 7 and had this problem immediately after installing pip. In case the above solutions don’t help you, you should check that the folder that pip.exe is installed in (in my case, the Script folder under Python32) is in the Path.
Check whether the pip-script points out the exact location of python.exe, because pip always points (C:python3.3python.exe). In my system i’ve installed 2 versions of python i.e python2 & python3. I ve modified the home application of python.exe into python2.exe and python3.exe.
When i installed pip windows installer. it results me out with the error ” failed to create process”
When I came across this problem, I found that my path contained multiple entries for Python. After tidying up my path so that it had an entry for the python installation folder and the scripts folder (in my case C:Python27 and C:Python27Scripts), pip worked properly.
Just ran into this. Sort of. Pip worked for me, but after installing pytest-watch, running the ptw script was giving this error.
For some reason, pip stopped quoting the #! in ptw-script.py:
#!C:Program Files (x86)Pythonpython.exe
It worked after I added quotes manually:
#!"C:Program Files (x86)Pythonpython.exe"
I don’t really know why this suddenly started happening. Adding this here in case anyone else coming here from Google runs into the same thing.
Here’s a related pip issue (I think).
It will help after changing the PATH to python in environment variables:
python -m pip install --upgrade pip --force-reinstall
Please check out have you ever rename your python.exe
I install python2 and python3 on my PC at the same time , so I rename my python.exe to python3.exe.And when I use pip ,it boom…
After rename it back .It’s ok again….
I ran into this bug while installing an older version of Python (3.5.2) for compatibility with some aws-adfs scripting. I installed aws-adfs with pip, on Windows 10, and found that while Python is installed to a directory path with spaces in it you will get the failed to create process error.
The pip maintainers say that it was a deeper problem with setuptools and even offered a workaround if you want to patch the installation in place.
But another, easier solution if you’re working with older versions of Python is just to reinstall Python to a directory without spaces.
Running command prompt with administrator privileges worked for me.
To fix this error (after you change the folder where python is installed) run force-reinstall for pip and pyinstaller, like this:
python -m pip install --upgrade pip --force-reinstall
python -m pip install --upgrade pyinstaller --force-reinstall
Test this. it’s worked correctly for me:
python -m pip install –upgrade pip –force-reinstall
I had the same problem and none of the above worked for me.
I deleted my venv. And created a new one by specifying the python path:
virtualenv --python C:PathToPythonpython.exe venv
.venvScriptsactivate
and this worked
After following this article: How do I install pip on Windows? on my Windows system using Enthought Canopy 64 Bit system, I cannot get pip or easy_install to work due to error:
pip install requests
failed to create process
I tried re-installing setuptools, running cmd prompt as admin without any effect.
When I encountered this, it was because I’d manually renamed the directory python was in. This meant that both setuptools and pip had to be reinstalled. Or, I had to manually rename the python directory to what it had been previously.
If you intentionally want to rename the folder where python.exe resides, you should also modify all python files in the Scripts folder. So a third solution would be to modify the python files as well: the first line in pip-2.7-script.py originally contain:
#!C:OriginalPythonDirpython.exe
Modifying this path to the new Python folder fixes the problem.
(P.S. Unfortunately I cannot yet reply to answers, so I’ll reply as a new answer because I thought it could be useful for other people as well).
I had installed Anaconda and so I still had C:Python27 along with C:Anaconda in my path. When I removed C:Python27 and all subfolders I was able to use pip again.
I just use python in the command shell on Windows 7 and had this problem immediately after installing pip. In case the above solutions don’t help you, you should check that the folder that pip.exe is installed in (in my case, the Script folder under Python32) is in the Path.
Check whether the pip-script points out the exact location of python.exe, because pip always points (C:python3.3python.exe). In my system i’ve installed 2 versions of python i.e python2 & python3. I ve modified the home application of python.exe into python2.exe and python3.exe.
When i installed pip windows installer. it results me out with the error ” failed to create process”
When I came across this problem, I found that my path contained multiple entries for Python. After tidying up my path so that it had an entry for the python installation folder and the scripts folder (in my case C:Python27 and C:Python27Scripts), pip worked properly.
Just ran into this. Sort of. Pip worked for me, but after installing pytest-watch, running the ptw script was giving this error.
For some reason, pip stopped quoting the #! in ptw-script.py:
#!C:Program Files (x86)Pythonpython.exe
It worked after I added quotes manually:
#!"C:Program Files (x86)Pythonpython.exe"
I don’t really know why this suddenly started happening. Adding this here in case anyone else coming here from Google runs into the same thing.
Here’s a related pip issue (I think).
It will help after changing the PATH to python in environment variables:
python -m pip install --upgrade pip --force-reinstall
Please check out have you ever rename your python.exe
I install python2 and python3 on my PC at the same time , so I rename my python.exe to python3.exe.And when I use pip ,it boom…
After rename it back .It’s ok again….
I ran into this bug while installing an older version of Python (3.5.2) for compatibility with some aws-adfs scripting. I installed aws-adfs with pip, on Windows 10, and found that while Python is installed to a directory path with spaces in it you will get the failed to create process error.
The pip maintainers say that it was a deeper problem with setuptools and even offered a workaround if you want to patch the installation in place.
But another, easier solution if you’re working with older versions of Python is just to reinstall Python to a directory without spaces.
Running command prompt with administrator privileges worked for me.
To fix this error (after you change the folder where python is installed) run force-reinstall for pip and pyinstaller, like this:
python -m pip install --upgrade pip --force-reinstall
python -m pip install --upgrade pyinstaller --force-reinstall
Test this. it’s worked correctly for me:
python -m pip install –upgrade pip –force-reinstall
I had the same problem and none of the above worked for me.
I deleted my venv. And created a new one by specifying the python path:
virtualenv --python C:PathToPythonpython.exe venv
.venvScriptsactivate
and this worked