[SPARK-58229][PYSPARK] Make graphviz requirement to match the documentation#57386
Open
gaogaotiantian wants to merge 2 commits into
Open
[SPARK-58229][PYSPARK] Make graphviz requirement to match the documentation#57386gaogaotiantian wants to merge 2 commits into
gaogaotiantian wants to merge 2 commits into
Conversation
zhengruifeng
approved these changes
Jul 21, 2026
uros-b
approved these changes
Jul 21, 2026
uros-b
left a comment
uros-b
left a comment
Member
There was a problem hiding this comment.
Thank you @gaogaotiantian and @zhengruifeng!
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
3 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?
Use
graphviz>=0.20instead ofgraphviz==0.20.3.Why are the changes needed?
In our documentation we claim to support
graphviz>=0.20, we should make the basic dependency match that claim.This will make it not conflict with our minimum CI test where it actually tests against the minimum supported version
0.20.0.Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI.
Was this patch authored or co-authored using generative AI tooling?
No.