| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| |
|
|
| |
count behavior.
|
| | |
|
| | |
|
| |
|
|
|
| |
PyUnicode_Find().
This closes SF bug #566631.
|
| |
|
|
|
| |
PyMarshal_WriteObjectToFile().
This closes SF bug #533735.
|
| |
|
|
|
| |
based on comments from David Abrahams.
Added refcount information for these functions.
|
| |
|
|
|
| |
constributed by David Abrahams.
This closes SF patch #568081.
|
| |
|
|
|
|
|
|
|
| |
Typo: whcar_t should be wchar_t.
Bugfix candidate? Don't know how this is handled in the docs.
Original patch(es):
python/dist/src/Doc/api/concrete.tex:1.15
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Repair widespread misuse of _PyString_Resize. Since it's clear people
don't understand how this function works, also beefed up the docs. The
most common usage error is of this form (often spread out across gotos):
if (_PyString_Resize(&s, n) < 0) {
Py_DECREF(s);
s = NULL;
goto outtahere;
}
The error is that if _PyString_Resize runs out of memory, it automatically
decrefs the input string object s (which also deallocates it, since its
refcount must be 1 upon entry), and sets s to NULL. So if the "if"
branch ever triggers, it's an error to call Py_DECREF(s): s is already
NULL! A correct way to write the above is the simpler (and intended)
if (_PyString_Resize(&s, n) < 0)
goto outtahere;
Bugfix candidate.
Original patch(es):
python/dist/src/Doc/api/concrete.tex:1.13
|
| |
|
|
| |
Update description of PyType_Check().
|
| |
|
|
| |
This closes SF bug #539081.
|
| |
|
|
|
|
|
| |
exceptions.tex 1.5
fix a typo in PyErr_Format table and add row for 'p' format char
closes bug 534495
|
| |
|
|
|
| |
other PyObject *.
This closes SF bug #494007.
|
| |
|
|
|
| |
(with only minor changes by Fred).
This closes SF bug #498607.
|
| |
|
|
| |
This closes SF bug #520087.
|
| |
|
|
|
|
| |
This closes SF patch #496215.
Add a little more detail to the example that had not been closed.
|
| | |
|
| |
|
|
|
|
|
| |
PyDict_UpdateFromSeq2(): removed it.
PyDict_MergeFromSeq2(): made it public and documented it.
PyDict_Merge() docs: updated to reveal <wink> that the second
argument can be any mapping object.
|
| |
|
|
| |
This closes SF bug #489872.
|
| |
|
|
|
| |
is not handled properly.
This closes SF bug #485153.
|
| |
|
|
|
|
| |
of references that now state that these attributes have been removed,
directing the reader to the dir() function.
This closes SF bug #456420.
|
| |
|
|
| |
This closes SF bug #488387.
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
supports the single-segment readable buffer interface.
Add documentation for this and other PyObject_XXXBuffer() calls.
|
| | |
|
| |
|
|
| |
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.
|
| | |
|