From b85fbec83ba3f423e6675ceb3b0630634ba9411e Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Mon, 13 Apr 1998 00:50:04 +0000 Subject: "ZeroDevisionError" --> "ZeroDivisionError" Thanks, AMK! --- Doc/ext.tex | 2 +- Doc/ext/ext.tex | 2 +- 2 files changed, 2 insertions(+), 2 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 diff --git a/Doc/ext/ext.tex b/Doc/ext/ext.tex index fc56a80..01d2428 100644 --- a/Doc/ext/ext.tex +++ b/Doc/ext/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 -- cgit v0.12