summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>1998-04-03 05:02:28 (GMT)
committerFred Drake <fdrake@acm.org>1998-04-03 05:02:28 (GMT)
commit7e9d3148d124a14395378f3ee16b773e50da53e0 (patch)
treed7acebc0d1631c05106287007d86104d4fe8f59d /Doc
parent6a79be8db82dd19ba69dcac5f4b10225db5f4064 (diff)
downloadcpython-7e9d3148d124a14395378f3ee16b773e50da53e0.zip
cpython-7e9d3148d124a14395378f3ee16b773e50da53e0.tar.gz
cpython-7e9d3148d124a14395378f3ee16b773e50da53e0.tar.bz2
Capitalize "Python" for consistency.
Diffstat (limited to 'Doc')
-rw-r--r--Doc/api.tex2
-rw-r--r--Doc/api/api.tex2
2 files changed, 2 insertions, 2 deletions
diff --git a/Doc/api.tex b/Doc/api.tex
index 942c30a..e0c3ad2 100644
--- a/Doc/api.tex
+++ b/Doc/api.tex
@@ -2014,7 +2014,7 @@ The current implementation keeps an array of integer objects for all
integers between \code{-1} and \code{100}, when you create an int in
that range you actually just get back a reference to the existing
object. So it should be possible to change the value of \code{1}. I
-suspect the behaviour of python in this case is undefined. :-)
+suspect the behaviour of Python in this case is undefined. :-)
\end{cfuncdesc}
\begin{cfuncdesc}{long}{PyInt_AS_LONG}{PyIntObject *io}
diff --git a/Doc/api/api.tex b/Doc/api/api.tex
index 942c30a..e0c3ad2 100644
--- a/Doc/api/api.tex
+++ b/Doc/api/api.tex
@@ -2014,7 +2014,7 @@ The current implementation keeps an array of integer objects for all
integers between \code{-1} and \code{100}, when you create an int in
that range you actually just get back a reference to the existing
object. So it should be possible to change the value of \code{1}. I
-suspect the behaviour of python in this case is undefined. :-)
+suspect the behaviour of Python in this case is undefined. :-)
\end{cfuncdesc}
\begin{cfuncdesc}{long}{PyInt_AS_LONG}{PyIntObject *io}