Use the highest available pickle protocol #160
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
cburgdorf
force-pushed
the
christoph/fix/pickle-latest-protocol
branch
2 times, most recently
from
d435076
to
02306be
Compare
cburgdorf
force-pushed
the
christoph/fix/pickle-latest-protocol
branch
from
02306be
to
5d0fe38
Compare
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 was wrong?
On Python < 3.8 (which isn't released yet) pickle still uses version
3of the protocol by default (even though version4is already available. Python 3.8 will make version5the default protocol.How was it fixed?
Always use the highest available pickle protocol.
To-Do
Cute Animal Picture