Bump minimum cloudpickle to 3
#8836
Merged
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
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 25 files ±0 25 suites ±0 10h 8m 3s ⏱️ - 3m 51s For more details on these failures, see this check. Results for commit ee37ced. ± Comparison against base commit cdad3cb. ♻️ This comment has been updated with latest results. |
phofl
approved these changes
Aug 19, 2024
|
thx |
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.
dask/dask#11320 bumped our
cloudpickleversion constraint to becloudpickle >= 3.0.0. Givendistributedpins tightly todask, we transitively will always pull incloudpickle >= 3.0.0anyways. This PR just formally bumps the pinning indistributedto match that indask. Not a functional change, just housekeeping.