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.  ;-(

diff --git a/Doc/lib/libcopy.tex b/Doc/lib/libcopy.tex
index f931c0283091f25abe0bd822cea50dac764e90ff..d73d6fdecf9c6473175c2cc58b6a3e17bd8f7f3d 100644 (file)
--- a/Doc/lib/libcopy.tex
+++ b/Doc/lib/libcopy.tex
@@ -72,14 +72,10 @@ stack trace, stack frame, file, socket, window, array, or any similar
 types.
 
 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
+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.
-\withsubitem{(copy protocol)}{\ttindex{__getinitargs__()}
-  \ttindex{__getstate__()}\ttindex{__setstate__()}}
 
 In order for a class to define its own copy implementation, it can
 define special methods \method{__copy__()} and