[Python-checkins] CVS: python/dist/src/Doc/lib libpickle.tex,1.32,1.33

2001年11月26日 13:30:38 -0800

Update of /cvsroot/python/python/dist/src/Doc/lib
In directory usw-pr-cvs1:/tmp/cvs-serv5872/lib
Modified Files:
	libpickle.tex 
Log Message:
Fix typo, extra markup constructs.
This closes SF bug #485252.
Index: libpickle.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libpickle.tex,v
retrieving revision 1.32
retrieving revision 1.33
diff -C2 -d -r1.32 -r1.33
*** libpickle.tex	2001年11月18日 16:24:01	1.32
--- libpickle.tex	2001年11月26日 21:30:36	1.33
***************
*** 19,29 ****
 inverse operation, whereby a byte stream is converted back into an
 object hierarchy. Pickling (and unpickling) is alternatively known as
! ``serialization'', ``marshaling\footnote{Don't confuse this with the
! \module{marshal}\refmodule{marshal} module}'', or ``flattening'',
 however the preferred term used here is ``pickling'' and
 ``unpickling'' to avoid confusing.

 This documentation describes both the \module{pickle} module and the 
! \module{cPickle}\refmodule{cPickle} module.

 \subsection{Relationship to other Python modules}
--- 19,29 ----
 inverse operation, whereby a byte stream is converted back into an
 object hierarchy. Pickling (and unpickling) is alternatively known as
! ``serialization'', ``marshalling,''\footnote{Don't confuse this with
! the \refmodule{marshal} module} or ``flattening'',
 however the preferred term used here is ``pickling'' and
 ``unpickling'' to avoid confusing.

 This documentation describes both the \module{pickle} module and the 
! \refmodule{cPickle} module.

 \subsection{Relationship to other Python modules}
***************
*** 47,51 ****

 Python has a more primitive serialization module called
! \module{marshal}\refmodule{marshal}, but in general
 \module{pickle} should always be the preferred way to serialize Python
 objects. \module{marshal} exists primarily to support Python's
--- 47,51 ----

 Python has a more primitive serialization module called
! \refmodule{marshal}, but in general
 \module{pickle} should always be the preferred way to serialize Python
 objects. \module{marshal} exists primarily to support Python's
***************
*** 458,462 ****
 An alternative to implementing a \method{__reduce__()} method on the
 object to be pickled, is to register the callable with the
! \refmodule{copy_reg} module. This module provides a way
 for programs to register ``reduction functions'' and constructors for
 user-defined types. Reduction functions have the same semantics and
--- 458,462 ----
 An alternative to implementing a \method{__reduce__()} method on the
 object to be pickled, is to register the callable with the
! \refmodule[copyreg]{copy_reg} module. This module provides a way
 for programs to register ``reduction functions'' and constructors for
 user-defined types. Reduction functions have the same semantics and
***************
*** 598,602 ****
 which is not a class, the unpickler will check to make sure that the
 callable has either been registered as a safe callable via the
! \refmodule{copy_reg} module, or that it has an
 attribute \member{__safe_for_unpickling__} with a true value. This
 prevents the unpickling environment from being tricked into doing
--- 598,602 ----
 which is not a class, the unpickler will check to make sure that the
 callable has either been registered as a safe callable via the
! \refmodule[copyreg]{copy_reg} module, or that it has an
 attribute \member{__safe_for_unpickling__} with a true value. This
 prevents the unpickling environment from being tricked into doing