Respect and enable uninstalls of existing .egg-info
packages
#3380
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Users often find themselves dropped into environments that contain
.egg-info
packages. While we won't support installing these, it's not hard to support identifying them (e.g., inpip freeze
) and uninstalling them.Closes #2841.
Closes #2928.
Closes #3341.
Test Plan
Ran
cargo run pip freeze --python /opt/homebrew/Caskroom/miniforge/base/envs/TEST/bin/python
, with an environment that includespip
as an.egg-info
(/opt/homebrew/Caskroom/miniforge/base/envs/TEST/lib/python3.12/site-packages/pip-24.0-py3.12.egg-info
):Then ran
cargo run pip uninstall
, verified thatpip
was uninstalled, and no longer listed inpip freeze
.