(spark) branch master updated: [SPARK-56889][PYTHON][DOC][FOLLOWUP] Note Python 3.10 support drop in the migration guide

[yi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

Yicong-Huang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/master by this push:
     new 31c6dc401ba7 [SPARK-56889][PYTHON][DOC][FOLLOWUP] Note Python 3.10 support drop in the migration guide
31c6dc401ba7 is described below

commit 31c6dc401ba760abb294e796e1edae61ffba63cc
Author: Yicong Huang <17...@users.noreply.github.com>
AuthorDate: Tue Sep 1 21:55:58 2026 +0000

    [SPARK-56889][PYTHON][DOC][FOLLOWUP] Note Python 3.10 support drop in the migration guide
    
    ### What changes were proposed in this pull request?
    
    This is a follow-up to [SPARK-56889](https://issues.apache.org/jira/browse/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.py` on master already declares `python_requires=">=3.11"`.
    
    ### Was this patch authored or co-authored using generative AI tooling?
    
    No.
    
    Closes #58320 from Yicong-Huang/SPARK-56889-migration-guide.
    
    Authored-by: Yicong Huang <17...@users.noreply.github.com>
    Signed-off-by: Yicong-Huang <17...@users.noreply.github.com>
---
 python/docs/source/migration_guide/pyspark_upgrade.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/python/docs/source/migration_guide/pyspark_upgrade.rst b/python/docs/source/migration_guide/pyspark_upgrade.rst
index b257ee49b7dd..b7e6f797f715 100644
--- a/python/docs/source/migration_guide/pyspark_upgrade.rst
+++ b/python/docs/source/migration_guide/pyspark_upgrade.rst
@@ -19,6 +19,10 @@
 Upgrading PySpark
 ==================
 
+Upgrading from PySpark 4.2 to 4.3
+---------------------------------
+* In Spark 4.3, Python 3.10 support was dropped in PySpark.
+
 Upgrading from PySpark 4.1 to 4.2
 ---------------------------------
 * In Spark 4.2, the minimum supported version for PyArrow has been raised from 15.0.0 to 18.0.0 in PySpark.


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org