-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Official support for python 3.12 and code clean-up after EOLed Python 3.6 and 3.7. #517
Official support for python 3.12 and code clean-up after EOLed Python 3.6 and 3.7. #517
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #517 +/- ##
==========================================
+ Coverage 83.44% 88.90% +5.46%
==========================================
Files 4 3 -1
Lines 725 550 -175
Branches 157 114 -43
==========================================
- Hits 605 489 -116
+ Misses 95 48 -47
+ Partials 25 13 -12
☔ View full report in Codecov by Sentry. |
… observe on my dev machine
…kle_version.txt file
@HyukjinKwon I cleaned up a lot of dead code. As a result, the code base is much simpler and Please feel free to have a look at this PR to let me know if you see potential problems. I still haven't tested with the downstream tests since their config need an update. I think we should do that before merging this PR. I will try to work a distinct PR against master to do that. I would also like to blackify the code base before the release, but again in a dedicated PR to be able to remove the blackification commit from the git blame history. |
(I will likely be able to test this w/ PySpark few weeks later. would be great if we don't block this by me, and merge this first - I will report/fix separately if there's any issue) |
Thank you very much @HyukjinKwon. BTW, if you know a way to run a fraction of the tests of PySpark with a patched nightly build with the dev version of cloudpickle as we do for Ray in #519 that would help automate this process. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #517 +/- ##
===========================================
+ Coverage 83.44% 96.07% +12.62%
===========================================
Files 4 3 -1
Lines 725 560 -165
Branches 157 116 -41
===========================================
- Hits 605 538 -67
+ Misses 95 11 -84
+ Partials 25 11 -14
☔ View full report in Codecov by Sentry. |
Yay, downstream CI is green! |
@pierreglaser I think this should be ready for review if your have the time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking great, thank you @ogrisel! Just one minor comment.
Let me merge and follow-up with a PR dedicated to using black to enforce a consistent code style automatically. |
### What changes were proposed in this pull request? This PR proposes to upgrade Cloudpickle from 2.2.1 to 3.0.0. ### Why are the changes needed? It includes official support of Python 3.12 (cloudpipe/cloudpickle#517) ### Does this PR introduce _any_ user-facing change? It includes official support of Python 3.12 (cloudpipe/cloudpickle#517) ### How was this patch tested? Relies on cloudpickle's unittests. Existing test cases should pass too. Closes #43989 from HyukjinKwon/SPARK-46080. Authored-by: Hyukjin Kwon <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
Apologies for being late. I tested all, and at least all CI seems working fine with PySpark. We upgraded cloudpickle to 3.0.0 for Apache Spark 4.0.0. |
This is a takeover of #514 by @hugovk to be able to:
master
,