summaryrefslogtreecommitdiffstats
path: root/Doc/lib/libpickle.tex
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1995-03-13 10:03:32 (GMT)
committerGuido van Rossum <guido@python.org>1995-03-13 10:03:32 (GMT)
commit6bb1adc7ee688be85b839b747cf25a9e6254cc22 (patch)
tree8cb910de69fa0322275e60763bfc93a1ea12386f /Doc/lib/libpickle.tex
parenta8a8d4aadd49e3776e2212318331105c939974b4 (diff)
downloadcpython-6bb1adc7ee688be85b839b747cf25a9e6254cc22.zip
cpython-6bb1adc7ee688be85b839b747cf25a9e6254cc22.tar.gz
cpython-6bb1adc7ee688be85b839b747cf25a9e6254cc22.tar.bz2
small changes by Soren Larsen
Diffstat (limited to 'Doc/lib/libpickle.tex')
-rw-r--r--Doc/lib/libpickle.tex10
1 files changed, 5 insertions, 5 deletions
diff --git a/Doc/lib/libpickle.tex b/Doc/lib/libpickle.tex
index a9d5fa4..5c01d36 100644
--- a/Doc/lib/libpickle.tex
+++ b/Doc/lib/libpickle.tex
@@ -8,7 +8,7 @@
\indexii{pickling}{objects}
The \code{pickle} module implements a basic but powerful algorithm for
-``pickling'' (a.k.a. serializing, marshalling or flattening) nearly
+``pickling'' (a.k.a.\ serializing, marshalling or flattening) nearly
arbitrary Python objects. This is a more primitive notion than
persistency --- although \code{pickle} reads and writes file objects,
it does not handle the issue of naming persistent objects, nor the
@@ -32,7 +32,7 @@ following correctly:
\item pointer sharing
-\item instances uf user-defined classes
+\item instances of user-defined classes
\end{itemize}
@@ -105,11 +105,11 @@ module.
\ttindex{__dict__}
Note that when class instances are pickled, their class's code and
-data is not pickled along with them. Only the instance data is
+data are not pickled along with them. Only the instance data are
pickled. This is done on purpose, so you can fix bugs in a class or
add methods and still load objects that were created with an earlier
version of the class. If you plan to have long-lived objects that
-will see many versions of a class, it may be worth to put a version
+will see many versions of a class, it may be worthwhile to put a version
number in the objects so that suitable conversions can be made by the
class's \code{__setstate__()} method.
@@ -157,7 +157,7 @@ the file argument.
It is possible to make multiple calls to \code{Pickler.dump()} or to
\code{Unpickler.load()}, as long as there is a one-to-one
-correspondence between pickler and \code{Unpickler} objects and
+correspondence between \code{Pickler} and \code{Unpickler} objects and
between \code{dump} and \code{load} calls for any pair of
corresponding \code{Pickler} and \code{Unpicklers}. {\em Warning}:
this is intended for pickling multiple objects without intervening