From: Georg Brandl Date: Sun, 17 Oct 2010 10:24:54 +0000 (+0000) Subject: #9105: move pickle warning to a bit more prominent location. X-Git-Tag: v3.2a4~488 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0036bcf8d8c7baf3c27c50d9e03e450ff93585db;p=thirdparty%2FPython%2Fcpython.git #9105: move pickle warning to a bit more prominent location. --- diff --git a/Doc/library/pickle.rst b/Doc/library/pickle.rst index 66d14723d438..24006e2f98d7 100644 --- a/Doc/library/pickle.rst +++ b/Doc/library/pickle.rst @@ -23,6 +23,12 @@ into an object hierarchy. Pickling (and unpickling) is alternatively known as "serialization", "marshalling," [#]_ or "flattening", however, to avoid 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 ------------------------------------ @@ -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 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 :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