[SPARK-58305][PYTHON] Clarify jinja2 usage#57477
Open
gaogaotiantian wants to merge 1 commit into
Open
Conversation
HyukjinKwon
approved these changes
Jul 23, 2026
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?
Moved
jinja2topandas_on_spark_extrain dependency groups. Removed if from all the lint/doc docker images. Added documentation about it as the other optional requirements for pandas on spark.Why are the changes needed?
jinja2was not well documented and it was misused in our CIs. It is a requirement to useto_latex, not doc related. That's also the only usage we have in pyspark code.Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI needs to pass - if docs/lint CI fails because
jinja2is removed, I need to investigate again. Otherwise it proves that this package is not used for docs/lint.Was this patch authored or co-authored using generative AI tooling?
No.