"ZeroDevisionError" --> "ZeroDivisionError"

Thanks, AMK!
This commit is contained in:
Fred Drake 1998-04-13 00:50:04 +00:00
parent a608febd5f
commit b85fbec83b
2 changed files with 2 additions and 2 deletions

View file

@ -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 The choice of which exception to raise is entirely yours. There are
predeclared \C{} objects corresponding to all built-in Python exceptions, 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 course, you should choose exceptions wisely --- don't use
\cdata{PyExc_TypeError} to mean that a file couldn't be opened (that \cdata{PyExc_TypeError} to mean that a file couldn't be opened (that
should probably be \cdata{PyExc_IOError}). If something's wrong with should probably be \cdata{PyExc_IOError}). If something's wrong with

View file

@ -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 The choice of which exception to raise is entirely yours. There are
predeclared \C{} objects corresponding to all built-in Python exceptions, 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 course, you should choose exceptions wisely --- don't use
\cdata{PyExc_TypeError} to mean that a file couldn't be opened (that \cdata{PyExc_TypeError} to mean that a file couldn't be opened (that
should probably be \cdata{PyExc_IOError}). If something's wrong with should probably be \cdata{PyExc_IOError}). If something's wrong with