-
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
Name canonicalization issue in pip uninstall #8609
Comments
Looks like it's fixed in #8054. |
@atugushev, I can still reproduce this using |
Checked on aff33ff: $ pip --version
pip 20.2.dev1 from /Users/albert/Projects/pip/src/pip (python 3.8)
$ pip install zope-interface
Collecting zope-interface
Using cached zope.interface-5.1.0-cp38-cp38-macosx_10_9_x86_64.whl (192 kB)
Requirement already satisfied: setuptools in ./.venv/lib/python3.8/site-packages (from zope-interface) (45.2.0)
Installing collected packages: zope-interface
Successfully installed zope-interface
$ pip list | grep zope
zope.interface 5.1.0
$ pip uninstall zope-interface
Found existing installation: zope.interface 5.1.0
Uninstalling zope.interface-5.1.0:
Would remove:
/Users/albert/Projects/pip/.venv/lib/python3.8/site-packages/zope.interface-5.1.0-py3.8-nspkg.pth
/Users/albert/Projects/pip/.venv/lib/python3.8/site-packages/zope.interface-5.1.0.dist-info/*
/Users/albert/Projects/pip/.venv/lib/python3.8/site-packages/zope/interface/*
Proceed (y/n)? |
Please have my apologies: you are correct, I was testing on an venv and it uses pip's latest release instead of the editable version. I can confirm that the problem is solved as of current master. |
Ah, perfect. Thanks for investigating this @atugushev. |
Environment
Description
pip uninstall should canonicalize names when determining if they are installed.
How to Reproduce
Expected result
In the example above, pip should have uninstalled
zope.interface
.This is easily worked around when used manually, but is more annoying when the uninstall command is invoked by tools working with canonical names.
The text was updated successfully, but these errors were encountered: