summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2000-09-09 03:28:00 (GMT)
committerFred Drake <fdrake@acm.org>2000-09-09 03:28:00 (GMT)
commit7acb21866c3d84908cd6d95dbbf9563bb5479a0e (patch)
treec0fa3c97a23e31a521fad05b0d32b662b29b1491
parente5441913970871837ab0a43bbf760f285c85f0f6 (diff)
downloadcpython-7acb21866c3d84908cd6d95dbbf9563bb5479a0e.zip
cpython-7acb21866c3d84908cd6d95dbbf9563bb5479a0e.tar.gz
cpython-7acb21866c3d84908cd6d95dbbf9563bb5479a0e.tar.bz2
Minor clarifications in the introductory paragraph.
-rw-r--r--Doc/lib/libexcs.tex13
1 files changed, 7 insertions, 6 deletions
diff --git a/Doc/lib/libexcs.tex b/Doc/lib/libexcs.tex
index 742004e..40cc6fd 100644
--- a/Doc/lib/libexcs.tex
+++ b/Doc/lib/libexcs.tex
@@ -4,12 +4,13 @@
\modulesynopsis{Standard exceptions classes.}
-Exceptions can be class objects or string objects. While
-traditionally most exceptions have been string objects, in Python
-1.5, all standard exceptions have been converted to class objects,
-and users are encouraged to do the same. The exceptions are defined
-in the module \module{exceptions}; this module never needs to be
-imported explicitly.
+Exceptions can be class objects or string objects. Though most
+exceptions have been string objects in past versions of Python, in
+Python 1.5 and newer versions, all standard exceptions have been
+converted to class objects, and users are encouraged to do the same.
+The exceptions are defined in the module \module{exceptions}. This
+module never needs to be imported explicitly: the exceptions are
+provided in the built-in namespace.
Two distinct string objects with the same value are considered different
exceptions. This is done to force programmers to use exception names