mirror of
https://github.com/python/cpython
synced 2026-09-29 12:10:30 +03:00
- add version annotation for HIGHEST_PROTOCOL
- cleaned up some markup
This commit is contained in:
parent
b7b1db9191
commit
7c4d8f3ca9
1 changed files with 5 additions and 5 deletions
|
|
@ -164,6 +164,7 @@ following constant:
|
|||
\begin{datadesc}{HIGHEST_PROTOCOL}
|
||||
The highest protocol version available. This value can be passed
|
||||
as a \var{protocol} value.
|
||||
\versionadded{2.3}
|
||||
\end{datadesc}
|
||||
|
||||
The \module{pickle} module provides the
|
||||
|
|
@ -255,12 +256,11 @@ including (but not necessarily limited to) \exception{AttributeError},
|
|||
|
||||
The \module{pickle} module also exports two callables\footnote{In the
|
||||
\module{pickle} module these callables are classes, which you could
|
||||
subclass to customize the behavior. However, in the \module{cPickle}
|
||||
modules these callables are factory functions and so cannot be
|
||||
subclassed. One of the common reasons to subclass is to control what
|
||||
subclass to customize the behavior. However, in the \refmodule{cPickle}
|
||||
module these callables are factory functions and so cannot be
|
||||
subclassed. One common reason to subclass is to control what
|
||||
objects can actually be unpickled. See section~\ref{pickle-sub} for
|
||||
more details.}, \class{Pickler} and
|
||||
\class{Unpickler}:
|
||||
more details.}, \class{Pickler} and \class{Unpickler}:
|
||||
|
||||
\begin{classdesc}{Pickler}{file\optional{, protocol\optional{, bin}}}
|
||||
This takes a file-like object to which it will write a pickle data
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue