Capitalize "Python" for consistency.
This commit is contained in:
parent
6a79be8db8
commit
7e9d3148d1
|
@ -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}
|
||||
|
|
|
@ -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}
|
||||
|
|
Loading…
Reference in New Issue