| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
PyErr_SetExcFromWindowsErr(), PyErr_SetExcFromWindowsErrWithFilename().
Similar to PyErr_SetFromWindowsErrWithFilename() and
PyErr_SetFromWindowsErr(), but they allow to specify
the exception type to raise. Available on Windows.
See SF patch #576458.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
more trivial lexical helper macros so that uses of these guys expand
to nothing at all when they're not enabled. This should help sub-
standard compilers that can't do a good job of optimizing away the
previous "(void)0" expressions.
Py_DECREF: There's only one definition of this now. Yay! That
was that last one in the family defined multiple times in an #ifdef
maze.
Py_FatalError(): Changed the char* signature to const char*.
_Py_NegativeRefcount(): New helper function for the Py_REF_DEBUG
expansion of Py_DECREF. Calling an external function cuts down on
the volume of generated code. The previous inline expansion of abort()
didn't work as intended on Windows (the program often kept going, and
the error msg scrolled off the screen unseen). _Py_NegativeRefcount
calls Py_FatalError instead, which captures our best knowledge of
how to abort effectively across platforms.
|
|
|
|
| |
line.
|
|
|
|
| |
PyErr_SetFromWindowsErrWithFilename().
|
|
|
|
|
| |
PyErr_SetFromWindowsErr().
Fixes SF# 576016, with additional markup.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
[ 400998 ] experimental support for extended slicing on lists
somewhat spruced up and better tested than it was when I wrote it.
Includes docs & tests. The whatsnew section needs expanding, and arrays
should support extended slices -- later.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Avoid checks for negative indices and duplicate checks for support of
the sequence protocol.
|
|
|
|
| |
Bugfix candidate? Don't know how this is handled in the docs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
SF Patch #547813.
|
| |
|
|
|
|
| |
Additional material is still needed in that section.
|
| |
|
|
|
|
| |
Small additional changes.
|
|
|
|
|
| |
Note that PyObject_Size() is a synonym for PyObject_Length().
This closes SF patch #544330 (contributed by Thomas Heller).
|
| |
|
| |
|
|
|
|
|
|
|
| |
(The real issue is whether modules can benefit from an alternate
implementation strategy rather than using a dictionary. We should migrate
away from direct dictionary manipulation to allow more room for Jeremy to
flex the implementation with changes in globals lookup.)
|
| |
|
|
|
|
| |
Update description of PyType_Check().
|
|
|
|
| |
used to define Python objects.
|
| |
|
|
|
|
|
| |
I probably didn't do a correct thing for the LaTeX spelling of the
integer 1.
|
|
|
|
|
|
|
|
| |
document to the C API reference. Move some instructional text from the API
reference to the Extending & Embedding manual.
Fix the descriptions of the es and es# formats for PyArg_Parse*().
This closes SF bug #536516.
|
|
|
|
| |
This closes SF bug #539081.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
descriptor, as used for the tp_methods slot of a type. These new flag
bits are both optional, and mutually exclusive. Most methods will not
use either. These flags are used to create special method types which
exist in the same namespace as normal methods without having to use
tedious construction code to insert the new special method objects in
the type's tp_dict after PyType_Ready() has been called.
If METH_CLASS is specified, the method will represent a class method
like that returned by the classmethod() built-in.
If METH_STATIC is specified, the method will represent a static method
like that returned by the staticmethod() built-in.
These flags may not be used in the PyMethodDef table for modules since
these special method types are not meaningful in that case; a
ValueError will be raised if these flags are found in that context.
|
|
|
|
| |
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.
|
|
|
|
| |
borrowed references.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|