[SPARK-50108][INFRA][PYTHON][TESTS] Upgrade PyPy CI to 3.10 #48647
Conversation
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
zhengruifeng
approved these changes
Oct 25, 2024
Member
Author
|
Thank you, @zhengruifeng . |
xinrong-meng
approved these changes
Oct 25, 2024
Member
|
LGTM, thank you! |
Member
Author
|
Thank you, @xinrong-meng . |
Member
Author
|
Merged to master for Apache Spark 4.0.0 on February 2025. |
Member
Author
|
For the record, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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 PR aims to upgrade
PyPyCI from 3.9 to 3.10.Why are the changes needed?
Since PyPy v7.3.18, Python 3.9 is dropped. To track the latest Python versions, we need to use PyPy 3.10.
Does this PR introduce any user-facing change?
No, this is an infra-only change.
How was this patch tested?
Pass the CIs for building image and manual review because this is a daily CI change.
Was this patch authored or co-authored using generative AI tooling?
No.