Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to run pip v. 10.0.0 with python 3.6.5 on Win 7 64 #5223
Unable to run pip v. 10.0.0 with python 3.6.5 on Win 7 64 #5223
auto-locked Outdated issues that have been locked by automation project: vendored dependency Related to a vendored dependency type: bug A confirmed bug or unintended behavior
Comments
Description:
Upgrading from version 9.0.3 causes pip not to work anymore with the error message:
Fatal error in launcher: Unable to create process using ‘»»c:\program files\python36\python.exe» «C:\Program Files\Python36\Scripts\pip.exe»
The same happens with pip3.exe or pip36.exe (of course, they are identical, but using them could help to solve path conflicts).
The only way to solve the problem was to rollback to version 9.0.3. (I also tried version 9.0.1 just as a distraction :-), and it worked too ).
Of course, I tried a plethora of solutions to be able to keep version 10.0.0, then I gave up and rolled back to version 9.0.3
What I’ve run:
From PowerShell or DOS window:
< python -m pip install -U pip >to upgrade pip to 10.0.0. Everything went well.
The text was updated successfully, but these errors were encountered:
This might be because of the script not updating. Does uninstalling pip and then reinstalling with get-pip.py improve the situation?
Note that you’d have to rename get-pip.py to not contain the word «pip» for it to work currently. (would be fixed in #5233)
@pfmoore do you have any inputs on this?
There is an extra quatation mark in the command, that caused this issue.
the wrong command
«»c:\program files\python36\python.exe» «C:\Program Files\Python36\Scripts\pip.exe»
the right command, see the difference.
«c:\program files\python36\python.exe» «C:\Program Files\Python36\Scripts\pip.exe»
@UserNotExist12 Well spotted, yes that would likely cause the problem. However, I’ve no idea why that extra quote would be appearing, or even what it’s appearing in. @lbauchi can you provide a better example of how to reproduce this? «Upgrading from version 9.0.3» isn’t that specific — it’s worked when I’ve done it.
One question, did you upgrade using «python -m pip install —upgrade pip» or «pip install —upgrade pip»? The latter is wrong (and this is noted in the docs) and will result in the 9.0.3 pip.exe script wrapper not being upgraded. There would have been an error if you’d done that. But even so, I have to say that I don’t know why that would result in the effects you’re seeing.
I upgraded pip using python -m pip install —upgrade pip and I have the same problem.
Fatal error in launcher: Unable to create process using ‘»»c:\program files\python36\python.exe» «C:\Program Files\Python36\Scripts\pip.exe»‘ with double quotation mark.
Thanks. I do not get the same behaviour (Windows 10 64-bit, Python 3.6.2 64-bit):
PS>python -m pip --version pip 9.0.3 from C:\Users\Gustav\.virtualenvs\5ba9a2da89fcba2\lib\site-packages (python 3.6) PS>python -m pip install --upgrade pip Collecting pip Using cached pip-10.0.0-py2.py3-none-any.whl Installing collected packages: pip Found existing installation: pip 9.0.3 Uninstalling pip-9.0.3: Successfully uninstalled pip-9.0.3 Successfully installed pip-10.0.0 PS>pip --version pip 10.0.0 from c:\users\gustav\.virtualenvs\5ba9a2da89fcba2\lib\site-packages\pip (python 3.6) OK. It appears to be because of the space in your path ( C:\Program Files\Python36\Scripts\pip.exe ). I have reproduced this using a virtualenv with a space in the pathname.
We’ll need to wait for a fix from distlib and then re-vendor. I don’t see an obvious way we can work around this in pip, unfortunately.
To revert pip version, I did following:
> python -m pip uninstall pip > python -m ensurepip > python -m pip install -U "pip and uninstall+install all other affected packages.
If needed we can downgrade our distlib too.
pradyunsg added type: bug A confirmed bug or unintended behavior project: vendored dependency Related to a vendored dependency labels Apr 15, 2018
@dstufft agreed, I want to give @vsajip time to look at the issue, but if he can't cut a release that fixes this in time, that's what I plan on doing. I have a feeling it reverts some other fixes that we'd like to get, though so it's definitely not the preferred option.
I have a feeling it reverts some other fixes that we'd like to get, though so it's definitely not the preferred option.
From #4819, it seems #923 would get un-fixed. 🙁
That's a bit worrying, as it implies that reverting might not fix this issue either 🙁
If I get some time, I'll try dropping the previous version of distlib into a pip installation and see if this problem still occurs. If it does, we may have to wait for a fix from distlib 🙁
BTW, we should add a test for running pip from a directory with spaces on it. Appveyor's setup doesn't use spaces, nor does my normal setup (I use a standard "per user" installation). But the CPython "All users" installation goes to "Program Files" - so it will be a common scenario and we need to test for it.
Same issue here, downgraded again to 9.0.3.
Pip version: 10.0.0 / 9.0.3
Python version: 3.6.3 64
Operating system: Win 10 64
distlib updated in the repo with a change which should fix this. Please verify the repo version fixes things, then I will cut a distlib version you can use to re-vendor in pip .
To help users to test this fix, I've created a branch distlib_fix in my clone of the pip repo https://github.com/pfmoore/pip. I tested the fix as follows:
>py -m venv "a b" >& '.\a b\Scripts\python.exe' -m pip install --upgrade 'git+https://github.com/pfmoore/pip@distlib_fix#egg=pip' Collecting pip from git+https://github.com/pfmoore/pip@distlib_fix#egg=pip Cloning https://github.com/pfmoore/pip (to distlib_fix) to c:\users\uk03306\appdata\local\temp\pip-build-8iltcg7r\pip Installing collected packages: pip Found existing installation: pip 9.0.1 Uninstalling pip-9.0.1: Successfully uninstalled pip-9.0.1 Running setup.py install for pip . done Successfully installed pip-10.0.0 >& '.\a b\Scripts\pip.exe' --version pip 10.0.0 from C:\Work\Scratch\a b\lib\site-packages\pip (python 3.6) At least in my test, I can confirm that the fix is working.
[実験 D] > pwd Path ---- C:\Users\taka\実験 D [実験 D] > python -m virtualenv virtualenv-pip10-pfmoore Using base prefix 'C:\\Users\\taka\\AppData\\Local\\Programs\\Python\\Python36-32' New python executable in C:\Users\taka\実験D~1\VI5F03~1\Scripts\python.exe Installing setuptools, pip, wheel. done. [実験 D] > .\virtualenv-pip10-pfmoore\Scripts\pip.exe -V pip 10.0.0 from c:\users\taka\実験d~1\vi5f03~1\lib\site-packages\pip (python 3.6) [実験 D] > .\virtualenv-pip10-pfmoore\Scripts\python.exe -m pip install -U https://github.com/pfmoor e/pip/archive/distlib_fix.zip Collecting https://github.com/pfmoore/pip/archive/distlib_fix.zip Downloading https://github.com/pfmoore/pip/archive/distlib_fix.zip (6.4MB) 100% |████████████████████████████████| 6.4MB 1.1MB/s Installing build dependencies . done Building wheels for collected packages: pip Running setup.py bdist_wheel for pip . done Stored in directory: C:\Users\taka\AppData\Local\Temp\pip-ephem-wheel-cache-gqsmkvtc\wheels\30\d4\19\3c45d45ab7d333f327892822f08f418d363b27b831b43ef815 Successfully built pip Installing collected packages: pip Found existing installation: pip 10.0.0 Uninstalling pip-10.0.0: Successfully uninstalled pip-10.0.0 Successfully installed pip-10.0.0 [実験 D] > .\virtualenv-pip10-pfmoore\Scripts\pip.exe -V pip 10.0.0 from c:\users\taka\実験 d\virtualenv-pip10-pfmoore\lib\site-packages\pip (python 3.6) [実験 D] > .\virtualenv-pip10-pfmoore\Scripts\pip.exe uninstall wheel -y Uninstalling wheel-0.31.0: Successfully uninstalled wheel-0.31.0 [実験 D] > .\virtualenv-pip10-pfmoore\Scripts\pip.exe install wheel Collecting wheel Using cached https://files.pythonhosted.org/packages/1b/d2/22cde5ea9af055f81814f9f2545f5ed8a053eb749c08d186b369959189a8/wheel-0.31.0-py2.py3-none-any.whl Installing collected packages: wheel Successfully installed wheel-0.31.0 [実験 D] > .\virtualenv-pip10-pfmoore\Scripts\wheel.exe -V usage: wheel [-h] . wheel: error: unrecognized arguments: -V [実験 D] > .\virtualenv-pip10-pfmoore\Scripts\python.exe -c "from pip._vendor import distlib; print( distlib.__version__)" 0.2.7.dev0 looks like distlib_fix fixes the pip issue as I am just a beginner in Python/Django I cannot test the advance things
now this warning pops up when I install something and yes PATH is already added to the environment variables
The script django-admin.exe is installed in 'C:\Users\Arjun Kharbanda\AppData\Local\Programs\Python\Python36\Scripts' which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location. Could you file a new issue for that?
Do mention what PATH is, in that issue.