[SPARK-47683][PYTHON][BUILD][FOLLOW-UP] Exclude lib/py4j*zip in pyspark-connect package#46331
Closed
HyukjinKwon wants to merge 1 commit into
Closed
[SPARK-47683][PYTHON][BUILD][FOLLOW-UP] Exclude lib/py4j*zip in pyspark-connect package#46331HyukjinKwon wants to merge 1 commit into
lib/py4j*zip in pyspark-connect package#46331HyukjinKwon wants to merge 1 commit into
Conversation
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.
What changes were proposed in this pull request?
This PR is a followup of #45053 that includes
lib/py4j*zipin the package. Currently it's being picked up by https://github.com/apache/spark/blob/master/python/MANIFEST.in#L26. For other files, we don't createdepsdirectory insetup.pyforpyspark-connectso they are not included. Butlibis being included.Why are the changes needed?
To exclude unrelated files.
Does this PR introduce any user-facing change?
No, the main change has not been released out yet.
How was this patch tested?
Manually packaged, and checked the contents via
vi.Was this patch authored or co-authored using generative AI tooling?
No.