summaryrefslogtreecommitdiffstats
path: root/Doc/api/abstract.tex
Commit message (Collapse)AuthorAgeFilesLines
* Fix API typo. The write buffer is not const. Closes SF 606216.Raymond Hettinger2002-09-081-1/+1
|
* Fix SF bug 587012, doc mentions inexistent builtin unistrNeal Norwitz2002-07-281-2/+2
|
* Clean up descriptions of PyObject_RichCompare() and PyObject_RichCompareBool()Fred Drake2002-06-141-8/+8
| | | | | based on comments from David Abrahams. Added refcount information for these functions.
* Add documentation for PyObject_RichCompare() and PyObject_RichCompareBool(),Fred Drake2002-06-131-0/+42
| | | | | constributed by David Abrahams. This closes SF patch #568081.
* Add version annotation for PySequence_ITEM().Fred Drake2002-05-231-1/+2
|
* Patch #552433: Special-case tuples. Avoid sub-type checking for lists.Martin v. Löwis2002-05-081-0/+7
| | | | | Avoid checks for negative indices and duplicate checks for support of the sequence protocol.
* Clarify the return value of PyObject_IsInstance().Fred Drake2002-04-231-8/+9
|
* Add documentation for PyObject_Call().Fred Drake2002-04-151-0/+16
| | | | | Note that PyObject_Size() is a synonym for PyObject_Length(). This closes SF patch #544330 (contributed by Thomas Heller).
* Correct the descriptions of the PyObject_As*Buffer() return values.Fred Drake2002-04-041-6/+6
| | | | This closes SF bug #539081.
* Documentation for PyObject_GetIter(), contributed by Greg ChapmanFred Drake2002-03-111-3/+18
| | | | | (with only minor changes by Fred). This closes SF bug #498607.
* Close an improperly-closed verbatim environment.Fred Drake2001-12-261-3/+6
| | | | | | | | This closes SF patch #496215. Add a little more detail to the example that had not been closed. Bugfix: this should be made part of 2.2.1.
* Clean up some markup cruft. A number of the macros that take noFred Drake2001-11-281-2/+2
| | | | | | | | parameters (like \UNIX) are commonly entered using an empty group to separate the markup from a following inter-word space; this is not needed when the next character is punctuation, or the markup is the last thing in the enclosing group. These cases were marked inconsistently; the empty group is now *only* used when needed.
* Fix obvious typos.Thomas Heller2001-11-121-3/+3
|
* Added version annotations, remove hard tabs.Fred Drake2001-11-091-7/+11
|
* Add PyObject_CheckReadBuffer(), which returns true if its argumentJeremy Hylton2001-11-091-0/+39
| | | | | | supports the single-segment readable buffer interface. Add documentation for this and other PyObject_XXXBuffer() calls.
* PyObject_CallFunctionObArgs() ---> PyObject_CallFunctionObjArgs()Fred Drake2001-10-281-7/+7
| | | | PyObject_CallMethodObArgs() ---> PyObject_CallMethodObjArgs()
* Added docs for PyObject_CallFunctionObArgs() and PyObject_CallMethodObArgs().Fred Drake2001-10-261-11/+32
| | | | Minor cleanups & markup consistency fixes.
* Generalize dictionary() to accept a sequence of 2-sequences. At theTim Peters2001-10-261-5/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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).
* Break the Python/C API manual into smaller files by chapter. This manualFred Drake2001-10-121-0/+842
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.