-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
conda doesn't correctly uninstalls packages installed by pip #10357
Comments
FYI -- we've been getting reports about failures like this since support for the REQUESTED file (from PEP 376) was added into pip. It was only when OP filed an issue detailing their entire sequence of reproduction steps (cross-linked by GitHub above) that we got to know what was likely the root cause of that issue. :) |
It took quite some trial-n-error to figure out that sequence. Thank you for the appreciation note, @pradyunsg. |
Hi there, thank you for your contribution! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment. Thanks! |
Hi, just wondering if anybody has looked at solving this? Still seems to be a problem... |
Current Behavior
conda does not remove all files listed in the RECORD metadata file when asked to remove a package. This leaves a corrupt distribution present, which other tools such as pip are unable to process.
Steps to Reproduce
Let's pick a package
pynvml
as an example:conda didn't delete the file listed in RECORD
This file wasn't in conda-forge build, but was added by pip - it seems conda removes only files that it installed,
So now the site-packages is broken and we can't use
pip
anymore:"Requirement already satisfied" is bogus since there is just one
REQUESTED
file that wasn't cleaned up in the dist dir.this fails too:
The only fix at the moment is to manually remove the dir by hand.
I have a package whose build process validates that the conda/pip installs worked correctly and so it happens to hit a similar sequence. But this can easily happen in real life, except install / uninstall commands can be called days apart...
Expected Behavior
conda and pip need to find a way to work better together ;)
I initially thought that it was a bug in pip, and filed a bug report there
pypa/pip#9129
but pip developers indicated that it's a bug in conda instead.
Thank you!
Environment Information
`conda info`
The text was updated successfully, but these errors were encountered: