summaryrefslogtreecommitdiff
path: root/Doc
diff options
context:
space:
mode:
authorKa-Ping Yee <ping@zesty.ca>2001-03-23 05:17:41 +0000
committerKa-Ping Yee <ping@zesty.ca>2001-03-23 05:17:41 +0000
commit54ca38a10c10f63be98991dc1082d7f514698f13 (patch)
tree96c023397590302d36a45b4a5ed192608060a4a5 /Doc
parent3c9e7fdf7317d674e980bc889e770ffe501682b1 (diff)
downloadcpython-54ca38a10c10f63be98991dc1082d7f514698f13.tar.gz
Give a slightly better explanation of excepthook.
Diffstat (limited to 'Doc')
-rw-r--r--Doc/lib/libsys.tex10
1 files changed, 6 insertions, 4 deletions
diff --git a/Doc/lib/libsys.tex b/Doc/lib/libsys.tex
index 44b7853738..be5a599a45 100644
--- a/Doc/lib/libsys.tex
+++ b/Doc/lib/libsys.tex
@@ -51,19 +51,21 @@ If \var{value} is not \code{None}, this function prints it to
\code{sys.displayhook} is called on the result of evaluating
an expression entered in an interactive Python session.
The display of these values can be customized by assigning
-another function to \code{sys.displayhook}.
+another one-argument function to \code{sys.displayhook}.
\end{funcdesc}
\begin{funcdesc}{excepthook}{\var{type}, \var{value}, \var{traceback}}
This function prints out a given traceback and exception to
\code{sys.stderr}.
-\code{sys.excepthook} is called when an exception is raised
-and uncaught. In an interactive session this happens just before
+When an exception is raised and uncaught, the interpreter calls
+\code{sys.excepthook} with three arguments, the exception class,
+exception instance, and a traceback object.
+In an interactive session this happens just before
control is returned to the prompt; in a Python program this happens
just before the program exits.
The handling of such top-level exceptions can be customized by
-assigning another function to \code{sys.excepthook}.
+assigning another three-argument function to \code{sys.excepthook}.
\end{funcdesc}
\begin{datadesc}{__displayhook__}