[Python-checkins] python/dist/src/Doc/lib libcopy.tex,1.16,1.17

[fdrake at users.sourceforge.net]

Update of /cvsroot/python/python/dist/src/Doc/lib
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8943

Modified Files:
	libcopy.tex 
Log Message:
Remove list of pickle protocol names used by the copy module; there
are enough subtleties to pickling that we don't want misunderstanding
to spread because we don't provide all the information twice.  The
reference to the pickle module for information will have to suffice;
at least only one portion of the docs will be out of date.  ;-(


Index: libcopy.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libcopy.tex,v
retrieving revision 1.16
retrieving revision 1.17
diff -C2 -d -r1.16 -r1.17
*** libcopy.tex	6 Oct 2000 20:16:50 -0000	1.16
--- libcopy.tex	5 May 2004 04:24:30 -0000	1.17
***************
*** 73,84 ****
  
  Classes can use the same interfaces to control copying that they use
! to control pickling: they can define methods called
! \method{__getinitargs__()}, \method{__getstate__()} and
! \method{__setstate__()}.  See the description of module
  \refmodule{pickle}\refstmodindex{pickle} for information on these
  methods.  The \module{copy} module does not use the
  \refmodule[copyreg]{copy_reg} registration module.
- \withsubitem{(copy protocol)}{\ttindex{__getinitargs__()}
-   \ttindex{__getstate__()}\ttindex{__setstate__()}}
  
  In order for a class to define its own copy implementation, it can
--- 73,80 ----
  
  Classes can use the same interfaces to control copying that they use
! to control pickling.  See the description of module
  \refmodule{pickle}\refstmodindex{pickle} for information on these
  methods.  The \module{copy} module does not use the
  \refmodule[copyreg]{copy_reg} registration module.
  
  In order for a class to define its own copy implementation, it can