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

Idea: Check for packages with 2 installed versions #2235

Closed
msabramo opened this issue Dec 20, 2014 · 5 comments
Closed

Idea: Check for packages with 2 installed versions #2235

msabramo opened this issue Dec 20, 2014 · 5 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@msabramo
Copy link
Contributor

If you end up with 2 egg-infos or dist-infos, weird stuff happens. IIRC, pip reports one of them only and it's not necessarily the one that gets loaded when code tries to import.

Folks sometimes run into this at my work where pip freeze tells them a new version is installed but the system exhibits behavior of the old version. Usually in this case, I advise doing pip uninstall twice, they look at me like "Seriously?", and then it fixes their problem.

This was the motivation behind my pip install -e PR #1552. But I don't know I there are other ways to get into that situation.

Maybe a pip check command? And maybe a pip freeze would do this check as well?

@msabramo msabramo changed the title Idea: Check for packages with 2 Idea: Check for packages with 2 installed versions Dec 20, 2014
@tritium21
Copy link

2 installed versions is not something generally supported in python (except with eggs, and pip does not deal with eggs). Unless I am missing something here...

@qwcode
Copy link
Contributor

qwcode commented Dec 20, 2014

yes, I agree this can happen on occasion, and it causes problems. there's an open PR for pip check already related to checking for conflicts or missing dependencies, but this makes sense as an additional check.

@msabramo
Copy link
Contributor Author

@qwcode: I assume you're referring to #1001 ?

@qwcode
Copy link
Contributor

qwcode commented Dec 21, 2014

@msabramo yes

@dstufft
Copy link
Member

dstufft commented Mar 22, 2017

Closing this. I believe that we've fixed the underlying problem that was causing this to happen making such a check no longer needed. If you run into this problem again please open a new issue for it.

@dstufft dstufft closed this as completed Mar 22, 2017
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 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

4 participants