From b32aa5ecef6c241d2415f2f5b90756f139e6e282 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Thu, 17 Aug 2000 22:29:31 +0000 Subject: [PATCH] Revise the comments about the exceptions module to not refer to source code; it is not sufficiently readable now that it in written in C, and is less likely to be available to end users. --- Doc/lib/libexcs.tex | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Doc/lib/libexcs.tex b/Doc/lib/libexcs.tex index 98793a23d62..13ec88bc706 100644 --- a/Doc/lib/libexcs.tex +++ b/Doc/lib/libexcs.tex @@ -5,11 +5,11 @@ Exceptions can be class objects or string objects. While -traditionally, most exceptions have been string objects, in Python +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 source code for those -exceptions is present in the standard library module -\module{exceptions}; this module never needs to be imported explicitly. +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. Two distinct string objects with the same value are considered different exceptions. This is done to force programmers to use exception names