Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
a092ba1a
Commit
a092ba1a
authored
Mar 21, 2003
by
Andrew M. Kuchling
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add PEP 307 section
parent
a978e106
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
44 additions
and
0 deletions
+44
-0
Doc/whatsnew/whatsnew23.tex
Doc/whatsnew/whatsnew23.tex
+44
-0
No files found.
Doc/whatsnew/whatsnew23.tex
View file @
a092ba1a
...
...
@@ -883,6 +883,50 @@ by Kevin Altis, Dave Cole, Andrew McNamara, Skip Montanaro, Cliff Wells.
\end{seealso}
%======================================================================
\section
{
PEP 307: Pickle Enhancements
\label
{
section-pep305
}}
The
\module
{
pickle
}
and
\module
{
cPickle
}
modules received some
attention during the 2.3 development cycle. In 2.2, new-style classes
could be pickled without difficult, but they weren't pickled very
compactly;
\pep
{
307
}
quotes a trivial example where a new-style class
results in a pickled string three times longer than that for a classic
class.
The solution was to invent a new pickle protocol. The
\function
{
pickle.dumps()
}
function has supported a text-or-binary flag
for a long time. In 2.3, this flag is redefined from a Boolean to an
integer; 0 is the old text-mode pickle format, 1 is the old binary
format, and now 2 is a new 2.3-specific format. (A new constant,
\constant
{
pickle.HIGHEST
_
PROTOCOL
}
, can be used to select the fanciest
protocol available.)
Unpickling is no longer considered a safe operation. 2.2's
\module
{
pickle
}
provided hooks for trying to prevent unsafe classes
from being unpickled (specifically, a
\member
{__
safe
_
for
_
unpickling
__}
attribute), but none of this code
was ever audited and therefore it's all been ripped out in 2.3. You
should not unpickle untrusted data in any version of Python.
To reduce the pickling overhead for new-style classes, a new interface
for customizing pickling was added using three special methods:
\method
{__
getstate
__}
,
\method
{__
setstate
__}
, and
\method
{__
getnewargs
__}
. Consult
\pep
{
307
}
for the full semantics
of these methods.
As a way to compress pickles yet further, it's now possible to use
integer codes instead of long strings to identify pickled classes.
The Python Software Foundation will maintain a list of standardized
codes; there's also a range of codes for private use. Currently no
codes have been specified.
\begin{seealso}
\seepep
{
307
}{
Extensions to the pickle protocol
}{
Written and implemented
by Guido van Rossum and Tim Peters.
}
\end{seealso}
%======================================================================
\section
{
Extended Slices
\label
{
section-slices
}}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment