mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-09-28 19:25:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

#9105: move pickle warning to a bit more prominent location.

Browse source
This commit is contained in:
Georg Brandl 2010-10-17 10:24:54 +00:00
parent 047e486c45
commit 0036bcf8d8
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
Doc/library/pickle.rst
View file

@ -23,6 +23,12 @@ into an object hierarchy. Pickling (and unpickling) is alternatively known as
"serialization", "marshalling," [#]_ or "flattening", however, to avoid "serialization", "marshalling," [#]_ or "flattening", however, to avoid
confusion, the terms used here are "pickling" and "unpickling".. confusion, the terms used here are "pickling" and "unpickling"..
.. warning::
The :mod:`pickle` module is not intended to be secure against erroneous or
maliciously constructed data. Never unpickle data received from an untrusted
or unauthenticated source.
Relationship to other Python modules Relationship to other Python modules
------------------------------------ ------------------------------------
@ -63,12 +69,6 @@ The :mod:`pickle` module differs from :mod:`marshal` several significant ways:
The :mod:`pickle` serialization format is guaranteed to be backwards compatible The :mod:`pickle` serialization format is guaranteed to be backwards compatible
across Python releases. across Python releases.
.. warning::
The :mod:`pickle` module is not intended to be secure against erroneous or
maliciously constructed data. Never unpickle data received from an untrusted
or unauthenticated source.
Note that serialization is a more primitive notion than persistence; although Note that serialization is a more primitive notion than persistence; although
:mod:`pickle` reads and writes file objects, it does not handle the issue of :mod:`pickle` reads and writes file objects, it does not handle the issue of
naming persistent objects, nor the (even more complicated) issue of concurrent naming persistent objects, nor the (even more complicated) issue of concurrent