[SPARK-46027][INFRA] Add Python 3.12 to the Daily Python Github Action job #43929
Conversation
This file contains 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
itholic
approved these changes
Nov 21, 2023
zhengruifeng
approved these changes
Nov 21, 2023
|
Merged to master. |
|
Thank you, @HyukjinKwon , @zhengruifeng , @itholic . :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR aims to enable
Python 3.12testing in the following dailyPython-onlyGithub Action job.https://github.com/apache/spark/actions/workflows/build_python.yml
Why are the changes needed?
To provide
Python 3.12test coverage to Apache Spark 4.0.0.Since SPARK-46020 installed
Python 3.12into the infra image, what we need is to add it to the daily job.Python 3.12to Infra docker image #43922Does this PR introduce any user-facing change?
No.
How was this patch tested?
We need to validate this in the daily GitHub Action job.
Was this patch authored or co-authored using generative AI tooling?
No.