[DOCS] add section for running pyspark with uv inline dependencies#54549
Open
markjm wants to merge 1 commit intoapache:masterfrom
Open
[DOCS] add section for running pyspark with uv inline dependencies#54549markjm wants to merge 1 commit intoapache:masterfrom
pyspark with uv inline dependencies#54549markjm wants to merge 1 commit intoapache:masterfrom
Conversation
64be50b to
2767621
Compare
2767621 to
b5261fe
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
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?
Added a doc section for running pyspark commands with
uv run. I do think it may be valuable to figure out a way to allow settingPYSPARK_PYTHONto a "composite" value (which has an executable + command) maybe, but this way works well.I have found this approach to be especially valuable in an environment with heterogenous python dependencies across a large organization. We have a "base" set of dependencies ambiently available to pyspark via installation in our docker container, but this allows applying changes or additions for specific use-cases.
I did not include much information about locking dependencies or other information and instead would rely on the
uv rundocs I linked to guide that part.Why are the changes needed?
They are not needed, but I figured I'd share back to the docs something which has worked well for me.
Does this PR introduce any user-facing change?
no
How was this patch tested?
I tried to build the docs with the dependencies in
dev/requirements.txtbut could not. I resorted to using those versions and directly runningNote: I also removed a trailing
;indev/requirements.txtwhich causeduv pip installto fail.Was this patch authored or co-authored using generative AI tooling?
No