summaryrefslogtreecommitdiff
path: root/Doc/lib/libexcs.tex
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1997-12-30 20:38:16 +0000
committerGuido van Rossum <guido@python.org>1997-12-30 20:38:16 +0000
commiteb0f066fb84e71f418cf6a27c38b128aee33a834 (patch)
treeb2695f000fd9119a7eabe7d7beff8c413ddcf097 /Doc/lib/libexcs.tex
parent51ca6e3e42d6ad733dae25c7db7c89415e7cf962 (diff)
downloadcpython-git-eb0f066fb84e71f418cf6a27c38b128aee33a834.tar.gz
Correct small nits reported by Rob Hooft.
Diffstat (limited to 'Doc/lib/libexcs.tex')
-rw-r--r--Doc/lib/libexcs.tex4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/lib/libexcs.tex b/Doc/lib/libexcs.tex
index 1a6ba40722..cd49af55f5 100644
--- a/Doc/lib/libexcs.tex
+++ b/Doc/lib/libexcs.tex
@@ -2,7 +2,7 @@
Exceptions can be class objects or string objects. While
traditionally, most exceptions have been string objects, in Python
-1.5a4, all standard exceptions have been converted to class objects,
+1.5, all standard exceptions have been converted to class objects,
and users are encouraged to the the same. The source code for those
exceptions is present in the standard library module
\code{exceptions}; this module never needs to be imported explicitly.
@@ -20,7 +20,7 @@ The string value of all built-in exceptions is their name, but this is
not a requirement for user-defined exceptions or exceptions defined by
library modules.
-For class exceptions, in a \code{try} statement with an\code{except}
+For class exceptions, in a \code{try} statement with an \code{except}
clause that mentions a particular class, that clause also handles
any exception classes derived from that class (but not exception
classes from which \emph{it} is derived). Two exception classes