mirror of
https://github.com/python/cpython.git
synced 2025-07-24 11:44:31 +00:00
Merged revisions 59605-59624 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk ........ r59606 | georg.brandl | 2007-12-29 11:57:00 +0100 (Sat, 29 Dec 2007) | 2 lines Some cleanup in the docs. ........ r59611 | martin.v.loewis | 2007-12-29 19:49:21 +0100 (Sat, 29 Dec 2007) | 2 lines Bug #1699: Define _BSD_SOURCE only on OpenBSD. ........ r59612 | raymond.hettinger | 2007-12-29 23:09:34 +0100 (Sat, 29 Dec 2007) | 1 line Simpler documentation for itertools.tee(). Should be backported. ........ r59613 | raymond.hettinger | 2007-12-29 23:16:24 +0100 (Sat, 29 Dec 2007) | 1 line Improve docs for itertools.groupby(). The use of xrange(0) to create a unique object is less obvious than object(). ........ r59620 | christian.heimes | 2007-12-31 15:47:07 +0100 (Mon, 31 Dec 2007) | 3 lines Added wininst-9.0.exe executable for VS 2008 Integrated bdist_wininst into PCBuild9 directory ........ r59621 | christian.heimes | 2007-12-31 15:51:18 +0100 (Mon, 31 Dec 2007) | 1 line Moved PCbuild directory to PC/VS7.1 ........ r59622 | christian.heimes | 2007-12-31 15:59:26 +0100 (Mon, 31 Dec 2007) | 1 line Fix paths for build bot ........ r59623 | christian.heimes | 2007-12-31 16:02:41 +0100 (Mon, 31 Dec 2007) | 1 line Fix paths for build bot, part 2 ........ r59624 | christian.heimes | 2007-12-31 16:18:55 +0100 (Mon, 31 Dec 2007) | 1 line Renamed PCBuild9 directory to PCBuild ........
This commit is contained in:
parent
862543aa85
commit
5b5e81c637
241 changed files with 19189 additions and 19152 deletions
|
@ -31,8 +31,8 @@ The error indicator consists of three Python objects corresponding to the result
|
|||
of ``sys.exc_info()``. API functions exist to interact with the error indicator
|
||||
in various ways. There is a separate error indicator for each thread.
|
||||
|
||||
.. % XXX Order of these should be more thoughtful.
|
||||
.. % Either alphabetical or some kind of structure.
|
||||
.. XXX Order of these should be more thoughtful.
|
||||
Either alphabetical or some kind of structure.
|
||||
|
||||
|
||||
.. cfunction:: void PyErr_Print()
|
||||
|
|
|
@ -264,7 +264,7 @@ Initialization, Finalization, and Threads
|
|||
as the list ``sys.path``, which may be modified to change the future search path
|
||||
for loaded modules.
|
||||
|
||||
.. % XXX should give the exact rules
|
||||
.. XXX should give the exact rules
|
||||
|
||||
|
||||
.. cfunction:: const char* Py_GetVersion()
|
||||
|
@ -357,8 +357,8 @@ Initialization, Finalization, and Threads
|
|||
to initialize ``sys.argv``, a fatal condition is signalled using
|
||||
:cfunc:`Py_FatalError`.
|
||||
|
||||
.. % XXX impl. doesn't seem consistent in allowing 0/NULL for the params;
|
||||
.. % check w/ Guido.
|
||||
.. XXX impl. doesn't seem consistent in allowing 0/NULL for the params;
|
||||
check w/ Guido.
|
||||
|
||||
|
||||
.. _threads:
|
||||
|
|
|
@ -484,7 +484,7 @@ Here is the corresponding C code, in all its glory::
|
|||
single: PyErr_Clear()
|
||||
single: Py_XDECREF()
|
||||
|
||||
This example represents an endorsed use of the :keyword:`goto` statement in C!
|
||||
This example represents an endorsed use of the ``goto`` statement in C!
|
||||
It illustrates the use of :cfunc:`PyErr_ExceptionMatches` and
|
||||
:cfunc:`PyErr_Clear` to handle specific exceptions, and the use of
|
||||
:cfunc:`Py_XDECREF` to dispose of owned references that may be *NULL* (note the
|
||||
|
|
|
@ -459,7 +459,7 @@ type objects) *must* have the :attr:`ob_size` field.
|
|||
declare the instance struct) and this in turn includes the :attr:`_ob_prev` and
|
||||
:attr:`_ob_next` fields if they are present. This means that the only correct
|
||||
way to get an initializer for the :attr:`tp_basicsize` is to use the
|
||||
:keyword:`sizeof` operator on the struct used to declare the instance layout.
|
||||
``sizeof`` operator on the struct used to declare the instance layout.
|
||||
The basic size does not include the GC header size (this is new in Python 2.2;
|
||||
in 2.1 and 2.0, the GC header size was included in :attr:`tp_basicsize`).
|
||||
|
||||
|
@ -1145,7 +1145,7 @@ The next fields, up to and including :attr:`tp_weaklist`, only exist if the
|
|||
|
||||
PyObject * tp_descr_get(PyObject *self, PyObject *obj, PyObject *type);
|
||||
|
||||
XXX more
|
||||
XXX explain.
|
||||
|
||||
This field is inherited by subtypes.
|
||||
|
||||
|
@ -1160,7 +1160,7 @@ The next fields, up to and including :attr:`tp_weaklist`, only exist if the
|
|||
|
||||
This field is inherited by subtypes.
|
||||
|
||||
XXX more
|
||||
XXX explain.
|
||||
|
||||
|
||||
.. cmember:: long PyTypeObject.tp_dictoffset
|
||||
|
@ -1683,10 +1683,9 @@ member in the :ctype:`PyTypeObject` structure should be *NULL*. Otherwise, the
|
|||
and :exc:`SystemError` should be raised when *segment* specifies a segment that
|
||||
doesn't exist.
|
||||
|
||||
.. % Why doesn't it raise ValueError for this one?
|
||||
.. % GJS: because you shouldn't be calling it with an invalid
|
||||
.. % segment. That indicates a blatant programming error in the C
|
||||
.. % code.
|
||||
.. Why doesn't it raise ValueError for this one?
|
||||
GJS: because you shouldn't be calling it with an invalid
|
||||
segment. That indicates a blatant programming error in the C code.
|
||||
|
||||
|
||||
.. ctype:: Py_ssize_t (*segcountproc) (PyObject *self, Py_ssize_t *lenp)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue