diff options
| author | Guido van Rossum <guido@python.org> | 1999-01-06 23:34:39 (GMT) |
|---|---|---|
| committer | Guido van Rossum <guido@python.org> | 1999-01-06 23:34:39 (GMT) |
| commit | cf3ce92ef4437ff028aea25f7e7e98a35ba30b49 (patch) | |
| tree | b3ba1345928bc9e028ab09be62755068b2df4156 | |
| parent | e51aa5b2cd537c2253c908bccd47e58bc195796b (diff) | |
| download | cpython-cf3ce92ef4437ff028aea25f7e7e98a35ba30b49.zip cpython-cf3ce92ef4437ff028aea25f7e7e98a35ba30b49.tar.gz cpython-cf3ce92ef4437ff028aea25f7e7e98a35ba30b49.tar.bz2 | |
Explain how come that pickle and cPickle, while using the same data
format, can produce different pickle strings for the same object.
| -rw-r--r-- | Doc/lib/libpickle.tex | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Doc/lib/libpickle.tex b/Doc/lib/libpickle.tex index 6f9ece7..cdfe3b7 100644 --- a/Doc/lib/libpickle.tex +++ b/Doc/lib/libpickle.tex @@ -294,3 +294,9 @@ subclassed. This should not be an issue in most cases. The format of the pickle data is identical to that produced using the \module{pickle} module, so it is possible to use \module{pickle} and \module{cPickle} interchangably with existing pickles. + +(Since the pickle data format is actually a tiny stack-oriented +programming language, and there are some freedoms in the encodings of +certain objects, it's possible that the two modules produce different +pickled data for the same input objects; however they will always be +able to read each others pickles back in.) |