Skip to content
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 install --upgrade pip breaks pip (new version 19.2.3) #6927

Closed
gneiss15 opened this issue Aug 26, 2019 · 4 comments
Closed

pip install --upgrade pip breaks pip (new version 19.2.3) #6927

gneiss15 opened this issue Aug 26, 2019 · 4 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@gneiss15
Copy link

  • Pip version: Installed 8..1.1, Updated version 19.2.3
  • Python version: 2.7.12
  • Operating system: Ubuntu 16.04 LTS

After doing a
pip install --upgrade pip
starting pip results in:
Traceback (most recent call last):
File "/usr/bin/pip", line 9, in
from pip import main
ImportError: cannot import name main

@triage-new-issues triage-new-issues bot added the S: needs triage Issues/PRs that need to be triaged label Aug 26, 2019
@userNeptune
Copy link

same problem here

@pradyunsg
Copy link
Member

Yea. There's nothing actionable here for pip developers -- Debian modifies the pip that they ship to users via apt, which breaks things in weird ways like this.

Please look at #5599.

@pfmoore
Copy link
Member

pfmoore commented Aug 27, 2019

But also, to be clear, you should not be upgrading system-supplied packages wihout using the system package manager (in this case apt) as explained in #5599 which @pradyunsg referenced.

@gneiss15
Copy link
Author

gneiss15 commented Aug 28, 2019

OK, that seams to be the problem.
Unfortunaly pip mentions/request to do the upgrade.
Is says something like:
a new version ... is available, please upgrade by using 'pip install...'
.. and after doing so, pip is broken :-(
OK, reinstaling it using apt solves the problem.
Who knows (before Your answer pfmoore) that ubuntu modifies pip ?

@chrahunt chrahunt removed the S: needs triage Issues/PRs that need to be triaged label Aug 31, 2019
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Sep 30, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Sep 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

5 participants