From 7acb21866c3d84908cd6d95dbbf9563bb5479a0e Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Sat, 9 Sep 2000 03:28:00 +0000 Subject: [PATCH] Minor clarifications in the introductory paragraph. --- Doc/lib/libexcs.tex | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/Doc/lib/libexcs.tex b/Doc/lib/libexcs.tex index 742004ede9..40cc6fd11f 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 -- 2.40.0