summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--Doc/lib/libexcs.tex4
-rw-r--r--Doc/libexcs.tex4
2 files changed, 4 insertions, 4 deletions
diff --git a/Doc/lib/libexcs.tex b/Doc/lib/libexcs.tex
index 863c7e1..1a6ba40 100644
--- a/Doc/lib/libexcs.tex
+++ b/Doc/lib/libexcs.tex
@@ -85,7 +85,7 @@ index used on a mapping or sequence is invalid: \code{IndexError},
\code{KeyError}.
\end{excdesc}
-\renewcommand{\indexsubitem}{(built-in exception base class)}
+\renewcommand{\indexsubitem}{(built-in exception)}
The following exceptions are the exceptions that are actually raised.
They are class objects, except when the \code{-X} option is used to
@@ -242,7 +242,7 @@ When class exceptions are used, the instance has an attribute
\code{code} which is set to the proposed exit status or error message
(defaulting to \code{None}).
- A call to \code{sys.exit} is translated into an exception so that
+ A call to \code{sys.exit()} is translated into an exception so that
clean-up handlers (\code{finally} clauses of \code{try} statements)
can be executed, and so that a debugger can execute a script without
running the risk of losing control. The \code{os._exit()} function
diff --git a/Doc/libexcs.tex b/Doc/libexcs.tex
index 863c7e1..1a6ba40 100644
--- a/Doc/libexcs.tex
+++ b/Doc/libexcs.tex
@@ -85,7 +85,7 @@ index used on a mapping or sequence is invalid: \code{IndexError},
\code{KeyError}.
\end{excdesc}
-\renewcommand{\indexsubitem}{(built-in exception base class)}
+\renewcommand{\indexsubitem}{(built-in exception)}
The following exceptions are the exceptions that are actually raised.
They are class objects, except when the \code{-X} option is used to
@@ -242,7 +242,7 @@ When class exceptions are used, the instance has an attribute
\code{code} which is set to the proposed exit status or error message
(defaulting to \code{None}).
- A call to \code{sys.exit} is translated into an exception so that
+ A call to \code{sys.exit()} is translated into an exception so that
clean-up handlers (\code{finally} clauses of \code{try} statements)
can be executed, and so that a debugger can execute a script without
running the risk of losing control. The \code{os._exit()} function