| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
PyObject_CallMethodObArgs() ---> PyObject_CallMethodObjArgs()
|
|
|
|
| |
Minor cleanups & markup consistency fixes.
|
|
|
|
| |
PyObject_CallMethodObArgs().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
outer level, the iterator protocol is used for memory-efficiency (the
outer sequence may be very large if fully materialized); at the inner
level, PySequence_Fast() is used for time-efficiency (these should
always be sequences of length 2).
dictobject.c, new functions PyDict_{Merge,Update}FromSeq2. These are
wholly analogous to PyDict_{Merge,Update}, but process a sequence-of-2-
sequences argument instead of a mapping object. For now, I left these
functions file static, so no corresponding doc changes. It's tempting
to change dict.update() to allow a sequence-of-2-seqs argument too.
Also changed the name of dictionary's keyword argument from "mapping"
to "x". Got a better name? "mapping_or_sequence_of_pairs" isn't
attractive, although more so than "mosop" <wink>.
abstract.h, abstract.tex: Added new PySequence_Fast_GET_SIZE function,
much faster than going thru the all-purpose PySequence_Size.
libfuncs.tex:
- Document dictionary().
- Fiddle tuple() and list() to admit that their argument is optional.
- The long-winded repetitions of "a sequence, a container that supports
iteration, or an iterator object" is getting to be a PITA. Many
months ago I suggested factoring this out into "iterable object",
where the definition of that could include being explicit about
generators too (as is, I'm not sure a reader outside of PythonLabs
could guess that "an iterator object" includes a generator call).
- Please check my curly braces -- I'm going blind <0.9 wink>.
abstract.c, PySequence_Tuple(): When PyObject_GetIter() fails, leave
its error msg alone now (the msg it produces has improved since
PySequence_Tuple was generalized to accept iterable objects, and
PySequence_Tuple was also stomping on the msg in cases it shouldn't
have even before PyObject_GetIter grew a better msg).
|
| |
|
| |
|
| |
|
|
|
|
| |
Prompted by Jim Ahlstrom. This closes SF patch #470614.
|
|
|
|
|
|
|
|
| |
has grown beyond what font-lock will work with using the default (X)Emacs
settings.
Indentation of the description has been made consistent, and a number of
smaller markup adjustments have been made as well.
|
| |
|
|
|
|
| |
This reflects what is currently in CVS, which may change before 2.2 is final.
|
| |
|
|
|
|
|
|
|
| |
introduced in Python 2.2.
Add documentation for the slice object interface (not complete).
Added version annotations for several of the Python 2.2 APIs already
documented.
|
| |
|
|
|
|
| |
Added signatures for some new PyType_*() functions.
|
|
|
|
| |
Document many more of the PyLong_{As,From}*() functions.
|
|
|
|
| |
Add refcount information for other recently documented APIs.
|
| |
|
|
|
|
| |
headers. This is the final checkin for SF bug #458768.
|
| |
|
|
|
|
| |
__builtin__.dir(). Moved the guts from bltinmodule.c to object.c.
|
| |
|
|
|
|
| |
Closes SF patch #455666.
|
|
|
|
| |
Closes SF patch #455666.
|
|
|
|
|
|
| |
description.
This fixes SF bug #453111.
|
| |
|
|
|
|
|
|
| |
created by Py_Initialize().
This closes SF bug #450621.
|
| |
|
|
|
|
|
|
| |
it has no such parameter.
This closes SF bug #449761.
|
|
|
|
|
|
|
| |
PyInterpreterState_*Head(), PyInterpreterState_Next(), and
PyThreadState_Next().
Wrapped some long lines, added some others.
|
|
|
|
| |
PyNumber_*TrueDivide().
|
|
|
|
|
|
|
| |
fragments when discussing equivalence of thhe C API to what a Python
programmer sees.
Added descriptions of PyEval_SetProfile() and PyEval_SetTrace().
|
|
|
|
|
|
| |
Moved the PyArg_Parse*(), Py_BuildValue() functions to the Utilities
chapter, added a minimal description and reference to the Extending
manual for Py_BuildValue().
|
| |
|
|
|
|
|
| |
tracing interface. Incomplete, but better to check it in since I've
been including it in my updates.
|
| |
|
|
|
|
|
|
| |
special character bite us again. ;-(
This fixes SF bug #440911.
|
|
|
|
|
|
| |
concrete sequence objects, since their API is simpler.
This is in response to a comment in SF bug #440037.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
PyObject_InitVar(), PyObject_Del(), PyObject_NEW(),
PyObject_NEW_VAR(), and PyObject_DEL().
Add notes to PyMem_Malloc() and PyMem_New() about the memory buffers
not being initialized.
This fixes SF bug #439012.
Added explicit return value information for PyList_SetItem(),
PyDict_SetItem(), and PyDict_SetItemString(). Corrected return type
for PyList_SET_ITEM().
Fixed index entries in the descriptions of PyLong_AsLong() and
PyLong_AsUnignedLong().
This fixes the API manual portion of SF bug #440037.
Note that the headers properly declare everything as 'extern "C"' for
C++ users.
Document _Py_NoneStruct.
Added links to the Extending & Embedding manual for PyArg_ParseTuple()
and PyArg_ParseTupleAndKeywords().
Added note that PyArg_Parse() should not be used in new code.
Fix up a few style nits -- avoid "e.g." and "i.e." -- these make
translation more difficult, as well as reading the English more
difficult for non-native speakers.
|
|
|
|
|
|
| |
The block/unblock thread macros are called 'Py_BLOCK_THREADS' and
'Py_UNBLOCK_THREADS', not 'Py_BEGIN_BLOCK_THREADS' and
'Py_BEGIN_UNBLOCK_THREADS'.
|
| |
|
|
|
|
| |
Add documentation for PyErr_SetFromErrnoWithFilename().
|
|
|
|
|
|
|
| |
In particular, the affect on existing list content was not sufficiently
explained.
This closes SF bug #429554.
|
|
|
|
|
|
|
| |
PySequence_Size(), not PyObject_Size(): the later considers the mapping
methods as well as the sequence methods, which is not needed here. Either
should be equally fast in this case, but PySequence_Size() offers a better
conceptual match.
|
|
|
|
|
|
| |
Added information on PyIter_Check(), PyIter_Next(),
PyObject_Unicode(), PyString_AsDecodedObject(),
PyString_AsEncodedObject(), and PyThreadState_GetDict().
|
|
|
|
|
|
|
|
| |
state *which* other function the current one is like, even if the
descriptions are adjacent.
Revise the _PyTuple_Resize() description to reflect the removal of the
third parameter.
|
| |
|
|
|
|
| |
This closes SF bug #425320.
|