[3.7] bpo-34621: backwards-compatible pickle UUID with is_safe=unknown#14834
Merged
taleinat merged 2 commits intoAug 4, 2019
Merged
Conversation
serhiy-storchaka
approved these changes
Jul 29, 2019
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Our previous fix for UUID pickling backwards-compatibility has a bug, where
SafeUUID.unknownis set in theis_safefield of the__getstate__state, rather thanis_safebeing omitted. This fixes that.Note that this doesn't happen in 3.8+, where the implementation is different due to the change of
UUIDto use slots.https://bugs.python.org/issue34621