You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Nicholas Chammas (Jira)" <ji...@apache.org> on 2026/09/02 16:38:00 UTC

[jira] [Resolved] (SPARK-31167) Refactor how we track Python test/build dependencies

     [ https://issues.apache.org/jira/browse/SPARK-31167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicholas Chammas resolved SPARK-31167.
--------------------------------------
    Resolution: Won't Fix

Superseded by later work like SPARK-58015.

> Refactor how we track Python test/build dependencies
> ----------------------------------------------------
>
>                 Key: SPARK-31167
>                 URL: https://issues.apache.org/jira/browse/SPARK-31167
>             Project: Spark
>          Issue Type: Improvement
>          Components: Build, Tests
>    Affects Versions: 3.1.0
>            Reporter: Nicholas Chammas
>            Priority: Minor
>
> Ideally, we should have a single place to track Python development dependencies and reuse it in all the relevant places: developer docs, Dockerfile, and GitHub CI. Where appropriate, we should pin dependencies to ensure a reproducible Python environment.



--
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