mirror of
https://github.com/python/cpython.git
synced 2025-08-03 00:23:06 +00:00
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. ;-(
This commit is contained in:
parent
cee8879a7d
commit
04d92c37f2
1 changed files with 1 additions and 5 deletions
|
@ -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
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue