diff options
| author | Fred Drake <fdrake@acm.org> | 1999-02-16 17:34:51 +0000 |
|---|---|---|
| committer | Fred Drake <fdrake@acm.org> | 1999-02-16 17:34:51 +0000 |
| commit | abfd7d6701e092da7955432dd1b48a99a2cdc1cb (patch) | |
| tree | eb1756da951b407849ab42255ba8ddbade3dc7f1 | |
| parent | 295fb434edfe397d61089d8839f4b8dd3df043a3 (diff) | |
| download | cpython-git-abfd7d6701e092da7955432dd1b48a99a2cdc1cb.tar.gz | |
Small grammatical fix; missing comma.
| -rw-r--r-- | Doc/ext/ext.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/ext/ext.tex b/Doc/ext/ext.tex index 93f8232098..1ae0421f3a 100644 --- a/Doc/ext/ext.tex +++ b/Doc/ext/ext.tex @@ -244,7 +244,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_ZeroDivisionError} 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 |