Remove legacy setup.py clean command#34443
Merged
Conversation
Contributor
Author
|
r: @kennknowles |
Contributor
|
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment |
liferoad
pushed a commit
to liferoad/beam
that referenced
this pull request
Apr 4, 2025
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
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.
I don't see any evidence of
python setup.py cleandoing any useful cleaning.In a clean repo, I have built apache-beam via:
python3 -m build --sdist, and also installed viapip install -e .This created 146 untracked files:
The number didn't change after running
python setup.py clean, so i don't see any value that it is adding, yet it requires additional deps and trips peoples's workflows.