From 331bfa4f2c3026a35e111303df0f198d06b4e0c8 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Sun, 9 Dec 2018 11:48:35 -0800 Subject: [PATCH] bpo-22005: Document the reality of pickle compatibility. (GH-11054) (cherry picked from commit e328753d91379274b699b93decff45de07854617) Co-authored-by: Gregory P. Smith --- Doc/library/pickle.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Doc/library/pickle.rst b/Doc/library/pickle.rst index 52cbb6241bc..36f66a159bf 100644 --- a/Doc/library/pickle.rst +++ b/Doc/library/pickle.rst @@ -71,7 +71,9 @@ The :mod:`pickle` module differs from :mod:`marshal` in several significant ways :file:`.pyc` files, the Python implementers reserve the right to change the serialization format in non-backwards compatible ways should the need arise. The :mod:`pickle` serialization format is guaranteed to be backwards compatible - across Python releases. + across Python releases provided a compatible pickle protocol is chosen and + pickling and unpickling code deals with Python 2 to Python 3 type differences + if your data is crossing that unique breaking change language boundary. Comparison with ``json`` ^^^^^^^^^^^^^^^^^^^^^^^^