-
Notifications
You must be signed in to change notification settings - Fork 3.1k
"No such file or directory" when trying to install or upgrade a package #6504
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
Comments
My guess (confirmation needed) is that Homebrew’s Python breaks how pip manages distributions, especially how it does in-place upgrade. If that is the case, this is likely more on Homebrew than pip (because pip can’t do much about it). |
Ok so I should post it in the Homebrew github page? |
@ZRunner, did you get this resolved or have any luck figuring out how to reproduce the issue? |
Yeah sorry I thought this issue was closed... so no I didn’t find a way to reproduce it, but I have some ideas. I think it was because I didn’t properly delete the old python version (installed with the website) before downloading the brew-version. Probably nothing that pip can do, except maybe add a security for this kind of case (clear useless folders to avoid confusion, or idk what). Thanks for the reply, and my apologies for the lack of answer :/ |
No worries! I'm glad that you were able to get unblocked. I think we're considering a few options in #6251 to address this situation (invalid |
I'm having this issue as well, albeit with WSL within an anaconda base environment: Here is the error in its entirety:
|
Environment
Description
I'm getting an error message when I try to use pip install/uninstall/upgrade commands, no matter what's the package is. The error is saying me pip 19.0.1 can't be found, but when I use
pip -V
it showspip 19.1.1 from /usr/local/lib/python3.7/site-packages/pip (python 3.7)
.I already try to uninstall python, without success. And about
pip-19.0.1.dist-info
mentionned in the report, this folder is completely empty. Not even hidden files.Also when I use
pip list --outdated
, pip is noted as using the 19.0.1.Expected behavior
Well, I expected no error. Sounds obvious but eh...
How to Reproduce
I didn't find how to reproduce this bug. I have no other Mac where to test and it works perfectly fine on my Debian 9 server.
Output
If I forgot any info, feel free to ask.
The text was updated successfully, but these errors were encountered: