[SPARK-56889][PYTHON][DOCS][FOLLOWUP] Note Python 3.10 support drop in the migration guide - #58320
Open
Yicong-Huang wants to merge 1 commit into
Open
[SPARK-56889][PYTHON][DOCS][FOLLOWUP] Note Python 3.10 support drop in the migration guide#58320Yicong-Huang wants to merge 1 commit into
Yicong-Huang wants to merge 1 commit into
Conversation
HyukjinKwon
approved these changes
Aug 27, 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?
This is a follow-up to SPARK-56889 (#55914), which dropped Python 3.10 support (PySpark now requires Python >= 3.11 on master). That PR did not add the corresponding entry to the PySpark migration guide. This PR adds a bullet to the "Upgrading from PySpark 4.2 to 4.3" section of
python/docs/source/migration_guide/pyspark_upgrade.rst, following the existing precedent for 4.1 (dropped 3.9) and 4.0 (dropped 3.8).Why are the changes needed?
Dropping a supported Python version is a user-facing change, and the migration guide should record it so users upgrading to the next release know 3.10 is no longer supported, consistent with how prior version drops were documented.
Does this PR introduce any user-facing change?
No. This is a documentation-only change; the actual support drop was made in SPARK-56889.
How was this patch tested?
Documentation-only change. Verified the new bullet matches the existing 4.1/4.0 precedent wording and that
python/packaging/classic/setup.pyon master already declarespython_requires=">=3.11".Was this patch authored or co-authored using generative AI tooling?
No.