[Python-checkins] python/dist/src/Doc/lib libpickle.tex,1.44,1.45

[fdrake at users.sourceforge.net]

Update of /cvsroot/python/python/dist/src/Doc/lib
In directory sc8-pr-cvs1:/tmp/cvs-serv29315

Modified Files:
	libpickle.tex 
Log Message:
- add version annotation for HIGHEST_PROTOCOL
- cleaned up some markup


Index: libpickle.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libpickle.tex,v
retrieving revision 1.44
retrieving revision 1.45
diff -C2 -d -r1.44 -r1.45
*** libpickle.tex	9 Sep 2003 19:49:18 -0000	1.44
--- libpickle.tex	10 Sep 2003 20:47:43 -0000	1.45
***************
*** 165,168 ****
--- 165,169 ----
  The highest protocol version available.  This value can be passed
  as a \var{protocol} value.
+ \versionadded{2.3}
  \end{datadesc}
  
***************
*** 256,265 ****
  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
  objects can actually be unpickled.  See section~\ref{pickle-sub} for
! more details.}, \class{Pickler} and
! \class{Unpickler}:
  
  \begin{classdesc}{Pickler}{file\optional{, protocol\optional{, bin}}}
--- 257,265 ----
  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 \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}:
  
  \begin{classdesc}{Pickler}{file\optional{, protocol\optional{, bin}}}