-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Update cloudpickle #8577
Update cloudpickle #8577
Conversation
Can one of the admins verify this patch? |
This is not a full update, but to see if the CI could run correctly. |
Test PASSed. |
Test PASSed. |
Test PASSed. |
Test PASSed. |
dfa3bca
to
527ec14
Compare
Test PASSed. |
Test FAILed. |
Test FAILed. |
jenkins retest this please |
Test FAILed. |
Ready for review. Some CI fails with |
|
@robertnishihara yes, there is modifications as we did before. It is from a recent release. Let me update init.py to include the release number. |
Test FAILed. |
@suquark can you remind me what the modifications are? Would they make sense to commit as part of cloudpickle? |
@robertnishihara the only difference is in the Later I would create a PR in the numpy upstream to enable pickle protocol5 support for python3.5, so we can remote the numpy polyfill. BTW, someone is working on pickle5 support (thus earlier python support) for cloudpickle: cloudpipe/cloudpickle#370. I think we should wait it merged, so then we can remove most of our changes. |
9383f08
to
abeceef
Compare
sync with master branch to retrigger CI builds |
Test FAILed. |
Ready to review. CI errors are same with the master branch, so they may be not related to this PR. |
FWIW I think PR ( cloudpipe/cloudpickle#370 ) is close, but it has a couple of test failures on 3.5 and 3.6 that I haven't quite worked out. Python 3.7 already works with those changes. It would be nice to get this to cross the line if we can. Any help that people here might be able to offer would be much appreciated 🙂 |
@jakirkham yes, I think we have figure out how to combine pickle5 protocol, pickle5-backport, and python3.5-3.8 properly in Ray for a while. After this PR is merged, I can try to commit these changes to the cloudpickle upstream. |
abeceef
to
1f7044c
Compare
(Rebase on master to get rid of some CI errors) |
@suquark when it comes to implementing pickling methods on classes ( From the cloudpickle side of things, my guess is we can optimize As to the particular test failures that I was stuck on earlier, Pierre has already helped sort those out. So I think mainly what we need at this stage is reviews from others. I can't comment too much on Ray's serialization logic as I'm less familiar. Though hopefully those ideas are useful. Please let us know if you have other thoughts 🙂 |
Diff to the upstream cloudpickle (v1.4.1): cloudpickle_fast.py:
|
EDIT: I made a mistake, it looks good, see above diff :) |
Test FAILed. |
Why are these changes needed?
Related issue number
Checks
scripts/format.sh
to lint the changes in this PR.