[SPARK-58747][PYTHON] Trim unnecessary commands from MANIFEST.in - #57973
Open
nchammas wants to merge 3 commits into
Open
[SPARK-58747][PYTHON] Trim unnecessary commands from MANIFEST.in#57973nchammas wants to merge 3 commits into
nchammas wants to merge 3 commits into
Conversation
uros-b
approved these changes
Aug 12, 2026
Member
|
LGTM |
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.
What changes were proposed in this pull request?
Trim unnecessary commands from MANIFEST.in. Tweak the various setup.py files to subsume their behavior.
MANIFEST.in
recursive-include ... *is recursive, whereas*in setuptools isn't. The equivalent in setuptools is to use**.Why are the changes needed?
Having duplicate (and unnecessary!) packaging specs across setup.py and MANIFEST.in is confusing.
The explicit
license_filesargument is not necessary -- setuptools packages these files by default -- but nice to have since it's explicit.Does this PR introduce any user-facing change?
No.
How was this patch tested?
I built the three sdists off of master and then again from this branch. I diffed their contents and found no differences.
I also repeated this test but by calling
./dev/make-distribution.sh --pipinstead ofpython ... sdist, sincemake-distribution.shstages license and JAR files before building the sdist. Again, no differences.Our CI packaging tests are a bit slim. I've separately proposed #57645 to make them more comprehensive.
Was this patch authored or co-authored using generative AI tooling?
I wrote the test scripts with assistance from GitHub Copilot.