[Python-checkins] python/dist/src/Doc/api abstract.tex, 1.26.12.2,
1.26.12.3 exceptions.tex, 1.15, 1.15.10.1 newtypes.tex,
1.23.8.2, 1.23.8.3
rhettinger at users.sourceforge.net
rhettinger at users.sourceforge.net
Sun Dec 7 06:43:58 EST 2003
Update of /cvsroot/python/python/dist/src/Doc/api
In directory sc8-pr-cvs1:/tmp/cvs-serv18153/api
Modified Files:
Tag: release23-maint
abstract.tex exceptions.tex newtypes.tex
Log Message:
SF patch #838938: Typos in the docs (Extending/Embedding + Python/C API)
(Contributed by Florent Rougon.)
Index: abstract.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/api/abstract.tex,v
retrieving revision 1.26.12.2
retrieving revision 1.26.12.3
diff -C2 -d -r1.26.12.2 -r1.26.12.3
*** abstract.tex 7 Sep 2003 02:26:54 -0000 1.26.12.2
--- abstract.tex 7 Dec 2003 11:43:56 -0000 1.26.12.3
***************
*** 268,272 ****
char *method, char *format,
\moreargs}
! Call the method named \var{m} of object \var{o} with a variable
number of C arguments. The C arguments are described by a
\cfunction{Py_BuildValue()} format string. The format may be \NULL,
--- 268,272 ----
char *method, char *format,
\moreargs}
! Call the method named \var{method} of object \var{o} with a variable
number of C arguments. The C arguments are described by a
\cfunction{Py_BuildValue()} format string. The format may be \NULL,
Index: exceptions.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/api/exceptions.tex,v
retrieving revision 1.15
retrieving revision 1.15.10.1
diff -C2 -d -r1.15 -r1.15.10.1
*** exceptions.tex 29 May 2003 02:17:22 -0000 1.15
--- exceptions.tex 7 Dec 2003 11:43:56 -0000 1.15.10.1
***************
*** 332,338 ****
The function is called with a single argument \var{obj} that
! identifies where the context in which the unraisable exception
! occurred. The repr of \var{obj} will be printed in the warning
! message.
\end{cfuncdesc}
--- 332,337 ----
The function is called with a single argument \var{obj} that
! identifies the context in which the unraisable exception occurred.
! The repr of \var{obj} will be printed in the warning message.
\end{cfuncdesc}
Index: newtypes.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/api/newtypes.tex,v
retrieving revision 1.23.8.2
retrieving revision 1.23.8.3
diff -C2 -d -r1.23.8.2 -r1.23.8.3
*** newtypes.tex 19 Oct 2003 07:31:14 -0000 1.23.8.2
--- newtypes.tex 7 Dec 2003 11:43:56 -0000 1.23.8.3
***************
*** 167,171 ****
the \ctype{PyObject} type; it is used when declaring new types which
represent objects without a varying length. The specific fields it
! expands to depends on the definition of
\csimplemacro{Py_TRACE_REFS}. By default, that macro is not
defined, and \csimplemacro{PyObject_HEAD} expands to:
--- 167,171 ----
the \ctype{PyObject} type; it is used when declaring new types which
represent objects without a varying length. The specific fields it
! expands to depend on the definition of
\csimplemacro{Py_TRACE_REFS}. By default, that macro is not
defined, and \csimplemacro{PyObject_HEAD} expands to:
***************
*** 398,402 ****
\cfunction{PyType_Ready()} checks if \member{ob_type} is \NULL, and
if so, initializes it: in Python 2.2, it is set to
! \code{\&PyType_Type}; in Python 2.2.1 and later it will be
initialized to the \member{ob_type} field of the base class.
\cfunction{PyType_Ready()} will not change this field if it is
--- 398,402 ----
\cfunction{PyType_Ready()} checks if \member{ob_type} is \NULL, and
if so, initializes it: in Python 2.2, it is set to
! \code{\&PyType_Type}; in Python 2.2.1 and later it is
initialized to the \member{ob_type} field of the base class.
\cfunction{PyType_Ready()} will not change this field if it is
***************
*** 705,709 ****
\begin{cmemberdesc}{PyTypeObject}{PyBufferProcs*}{tp_as_buffer}
! Pointer to an additional structure contains fields relevant only to
objects which implement the buffer interface. These fields are
documented in ``Buffer Object Structures'' (section
--- 705,709 ----
\begin{cmemberdesc}{PyTypeObject}{PyBufferProcs*}{tp_as_buffer}
! Pointer to an additional structure that contains fields relevant only to
objects which implement the buffer interface. These fields are
documented in ``Buffer Object Structures'' (section
More information about the Python-checkins
mailing list