-
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
Can't uninstall package installed with sudo pip install -e - "No files were found to uninstall." #5330
Comments
I have found similar problems uninstalling an editable install with any version of pip >= 10.0.0 Steps to reproduce are below. I'm using
I get the following error:
Python version: 2.7.12 |
i also get "uninstall" problems for packages which i installed with "pip install -e .". it's consistent and happens with newest virtualenv (16.0) and pip (10.0.1) on my ubu16.04. Downgrading to pip-0.9.3 fixes the issue, i can uninstall again. |
@FragLegs that looks different to me - if this is still affecting you please feel free to create a new issue so we can take a look. Hi @Poupine - the For the underlying issue, this looks like it could be the same as #5193. Can you provide clear instructions to reproduce this so we can confirm it? |
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
When installing a local package with
sudo -H pip3 install -e <path-to-my-package>
, my package is found and imported as expected, but the way it is done is possibly the worst that could possibly have been implemented ...Let me explain: what it does, is somehow adding
<path-to-my-package>
in my python path in some obscure way and when I runsudo -H pip3 uninstall <my-package-name>
, I am greeted with the following message:Can't uninstall '<my-package-name>'. No files were found to uninstall.
Where it becomes annoying is that even after deleting the egg-link file corresponding to my package from dist-packages, my python path still has the path to my library which means if my library is broken (which happened twice already in the span of 2 days with 2 different libraries), I am stuck with an unusable version of my library.
The only solution I have found so far to this, since I have no idea how the path to my library gets written to the python path, has been to wipe clean python and pip from my system and reinstall from scratch.
PS: Installing without -e has the correct behaviour (as in when I uninstall my package it actually does uninstall it).
The text was updated successfully, but these errors were encountered: