summaryrefslogtreecommitdiffstats
path: root/Doc/ext
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>1999-02-16 17:34:51 (GMT)
committerFred Drake <fdrake@acm.org>1999-02-16 17:34:51 (GMT)
commitabfd7d6701e092da7955432dd1b48a99a2cdc1cb (patch)
treeeb1756da951b407849ab42255ba8ddbade3dc7f1 /Doc/ext
parent295fb434edfe397d61089d8839f4b8dd3df043a3 (diff)
downloadcpython-abfd7d6701e092da7955432dd1b48a99a2cdc1cb.zip
cpython-abfd7d6701e092da7955432dd1b48a99a2cdc1cb.tar.gz
cpython-abfd7d6701e092da7955432dd1b48a99a2cdc1cb.tar.bz2
Small grammatical fix; missing comma.
Diffstat (limited to 'Doc/ext')
-rw-r--r--Doc/ext/ext.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/ext/ext.tex b/Doc/ext/ext.tex
index 93f8232..1ae0421 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