bpo-22005: Document the reality of pickle compatibility.#11054
Merged
gpshead merged 1 commit intopython:masterfrom Dec 9, 2018
Merged
bpo-22005: Document the reality of pickle compatibility.#11054gpshead merged 1 commit intopython:masterfrom
gpshead merged 1 commit intopython:masterfrom
Conversation
Contributor
|
Thanks @gpshead for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7. |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Dec 9, 2018
) (cherry picked from commit e328753) Co-authored-by: Gregory P. Smith <greg@krypto.org>
|
GH-11055 is a backport of this pull request to the 3.7 branch. |
miss-islington
added a commit
that referenced
this pull request
Dec 9, 2018
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.
People still seem surprised that pickle can't magically send bytes/str/unicode values back and forth from Python 2 and Python 3 processes without a lot of hand holding despite the underlying fundamental types of the language changing. This should clarify that there is no such free lunch.
It has always has been, impossible to guarantee such compatibility. That the docs were not updated to reflect this in 3.0 was an oversight.
https://bugs.python.org/issue22005