You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "kyungjunlee (Jira)" <ji...@apache.org> on 2025/07/14 00:36:00 UTC
[jira] [Commented] (SPARK-52785) Migrate from legacy super(Class, cls) to super() globally (for python 3)
[ https://issues.apache.org/jira/browse/SPARK-52785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18005021#comment-18005021 ]
kyungjunlee commented on SPARK-52785:
-------------------------------------
This is my first time creating a JIRA issue for Apache Spark, so please let me know if there's anything I should improve or correct. I'm happy to make any necessary adjustments.
If the issue is assigned to me, I’d love to try working on it myself.
> Migrate from legacy super(Class, cls) to super() globally (for python 3)
> ------------------------------------------------------------------------
>
> Key: SPARK-52785
> URL: https://issues.apache.org/jira/browse/SPARK-52785
> Project: Spark
> Issue Type: Improvement
> Components: PySpark
> Affects Versions: 4.0.0
> Reporter: kyungjunlee
> Priority: Minor
>
> Apache Spark has dropped support for Python 2 and now requires Python 3. However, some parts of the codebase still use the legacy `super(Class, cls)` syntax, which was originally used for compatibility with Python 2.
> ```
> super(MyClass, cls).setUpClass()
> ```
> This can now be simplified to the modern Python 3 style:
> ```
> super().setUpClass()
> ```
> This change has no functional impact, but it helps improve readability and modernize the codebase.
> I would like to work on replacing these legacy patterns throughout the codebase as my first contribution to Apache Spark.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org