Uninstall files recorded by legacy egg metadata - #223
Draft
zaniebot wants to merge 1 commit into
Draft
Conversation
zaniebot
force-pushed
the
zb/bughunt200/148-uninstall-egg-info-files
branch
from
July 16, 2026 02:34
9dc9972 to
bd43f06
Compare
zaniebot
force-pushed
the
zb/bughunt200/148-uninstall-egg-info-files
branch
from
July 16, 2026 05:47
bd43f06 to
82d75e9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Legacy egg-info uninstall ignores
installed-files.txtandentry_points.txt, leaving scripts and data files behind. Prefer recorded files, remove matching bytecode and launchers, and check paths before deleting them; this also avoids removing shared namespaces. Preserve the safety checks from uv#19114 and uv#19340 and follow pip's legacy uninstall.