-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
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
pip 6.0.8 AttributeError when upgrading to 6.1.1 in virtualenv #2669
Comments
So, this indicates that the finder didn't find the requested package. There's a reference to a closed issue 31 there in the code, but at a minimum we should be more defensive and report the parameters that failed ere. |
Thanks that's good to know. So it uninstalled/installed correctly, but then it goes back and tries to find the old version again which fails? |
That failure is in ScriptMaker, so I suspect it was at the point of making the pip.exe that it failed, and further that the uninstall rollback didn't really do much, so you've got a new pip.exe entrypoint which is importing the newly installed pip version, explaining the error you're seeing. To see if the bug is fixed, try doing a pip install -U --reinstall pip |
I get |
sorry, --force-reinstall |
yes, no errors this time. |
Another report of the same: http://paste.ubuntu.com/10787243/ followed by http://paste.ubuntu.com/10787273/ |
So both pip 6.0.8 and 1.5.6 fail to install 6.1.1 on Windows |
#2673 has another occurence of this. |
pip install --upgrade pip
|
I also experience this on Python 2.7.9 x64, on Windows 8.1
|
pip 1.5.6 failed to upgrade to 7.0.1 on python 3.4.3 on Windows
|
Same sh** with pip 7.1.0 with Python 2.7 on Window 7 64bit - see below. BUT HAPPILY H:\>pip install -U pip
You are using pip version 7.1.0, however version 7.1.2 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Collecting pip
Using cached pip-7.1.2-py2.py3-none-any.whl
Installing collected packages: pip
Found existing installation: pip 7.1.0
Uninstalling pip-7.1.0:
Successfully uninstalled pip-7.1.0
Rolling back uninstall of pip
Exception:
Traceback (most recent call last):
File "c:\python27\lib\site-packages\pip-7.1.0-py2.7.egg\pip\basecommand.py", line 223, in main
status = self.run(options, args)
File "c:\python27\lib\site-packages\pip-7.1.0-py2.7.egg\pip\commands\install.py", line 299, in run
root=options.root_path,
File "c:\python27\lib\site-packages\pip-7.1.0-py2.7.egg\pip\req\req_set.py", line 646, in install
**kwargs
File "c:\python27\lib\site-packages\pip-7.1.0-py2.7.egg\pip\req\req_install.py", line 813, in install
self.move_wheel_files(self.source_dir, root=root)
File "c:\python27\lib\site-packages\pip-7.1.0-py2.7.egg\pip\req\req_install.py", line 1008, in move_wheel_files
isolated=self.isolated,
File "c:\python27\lib\site-packages\pip-7.1.0-py2.7.egg\pip\wheel.py", line 449, in move_wheel_files
generated.extend(maker.make(spec))
File "c:\python27\lib\site-packages\pip-7.1.0-py2.7.egg\pip\_vendor\distlib\scripts.py", line 323, in make
self._make_script(entry, filenames, options=options)
File "c:\python27\lib\site-packages\pip-7.1.0-py2.7.egg\pip\_vendor\distlib\scripts.py", line 227, in _make_script
self._write_script(scriptnames, shebang, script, filenames, ext)
File "c:\python27\lib\site-packages\pip-7.1.0-py2.7.egg\pip\_vendor\distlib\scripts.py", line 163, in _write_script
launcher = self._get_launcher('t')
File "c:\python27\lib\site-packages\pip-7.1.0-py2.7.egg\pip\_vendor\distlib\scripts.py", line 302, in _get_launcher
result = finder(distlib_package).find(name).bytes
AttributeError: 'NoneType' object has no attribute 'bytes' |
Same problem on Windows 7 x64, pip 7.1.2, pypy 2.4.0 on initial installation using the
The trick with:
worked. |
I had the same problem, this worked for me http://stackoverflow.com/questions/31792591/error-while-upgrading-to-pip-7-1-10-on-windows-8-1-python-2-7/31799230#31799230 |
easy_install -U pip worked for me . Thanks 👍 |
easy_install -U pip worked for me too . Thanks for all |
Win 10 and Python 3.4.4, same error, the pip force reinstall thing didn't work but the easy_install -U pip did. |
Same here, using easy_install helped. |
Yep, same. Windows 10. Python 2.7.10.
The above command worked. |
Yes, the same error. Windows 10. Python 3.5.1. |
Windows 10. Python 2.7.12.
可以更新,不过如果Python安装在C盘可能没有权限操作文件会报错,用管理员权限启动cmd可以解决。 |
easy_install -U pip worked for me . Thanks 👍 |
please note that easy_install -U pip has some dire consequences as it does an egg based install instead of a sane install |
Closing this, if it continues to happen please reopen this issue or open a new one with reproduction steps. |
I was run 'python -m pip install -U --force-reinstall pip' , python 3.6 |
Getting the error on a Windows 10 virtualenv.
|
@OrangeDog I'm curious how you have pip 9.0.1 installed as an egg. That shouldn't happen usually. |
@pradyunsg interesting. |
Older versions of IntelliJ IDEA installed pip as an egg. I reported that some time ago (over a year, I think) and I thought they'd fixed it. Are you using an old version of IDEA? |
That was only one version ago, and the ticket is still open, so I guess that's why. |
I also faced this issue, when using Intellij IDEA to set up the virtualenv. Running |
|
I'm seeing this same problem trying to upgrade pip within a virtualenv that was created with pip 9.0.1 by PyCharm. |
This seems to be occurring again, with pip 9 -> pip 10 upgrades. Issue for that is #5343. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Windows 7, Python 3.4.3, updated pip in base. Created virtualenv, saw that it was still on pip 6.0.8
Activated venv, ran
python -m pip install pip -U
log:
However, next time I run pip -V, it reports pip 6.1.1, so what is the effect of the error?
The text was updated successfully, but these errors were encountered: