summaryrefslogtreecommitdiffstats
path: root/Doc/ext.tex
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>1998-04-13 00:50:04 (GMT)
committerFred Drake <fdrake@acm.org>1998-04-13 00:50:04 (GMT)
commitb85fbec83ba3f423e6675ceb3b0630634ba9411e (patch)
tree387a8b69126bfdfe3ab1f18470b035739a623c6b /Doc/ext.tex
parenta608febd5fe146f0eea6780402de15c09a9d9ff4 (diff)
downloadcpython-b85fbec83ba3f423e6675ceb3b0630634ba9411e.zip
cpython-b85fbec83ba3f423e6675ceb3b0630634ba9411e.tar.gz
cpython-b85fbec83ba3f423e6675ceb3b0630634ba9411e.tar.bz2
"ZeroDevisionError" --> "ZeroDivisionError"
Thanks, AMK!
Diffstat (limited to 'Doc/ext.tex')
-rw-r--r--Doc/ext.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/ext.tex b/Doc/ext.tex
index fc56a80..01d2428 100644
--- a/Doc/ext.tex
+++ b/Doc/ext.tex
@@ -240,7 +240,7 @@ you have already created) when you return an error indicator!
The choice of which exception to raise is entirely yours. There are
predeclared \C{} objects corresponding to all built-in Python exceptions,
-e.g. \cdata{PyExc_ZeroDevisionError} which you can use directly. Of
+e.g. \cdata{PyExc_ZeroDivisionError} which you can use directly. Of
course, you should choose exceptions wisely --- don't use
\cdata{PyExc_TypeError} to mean that a file couldn't be opened (that
should probably be \cdata{PyExc_IOError}). If something's wrong with