2007-08-15 11:28:22 -03:00
|
|
|
.. highlightlang:: c
|
|
|
|
|
|
|
|
|
|
|
|
.. _defining-new-types:
|
|
|
|
|
|
|
|
******************
|
|
|
|
Defining New Types
|
|
|
|
******************
|
|
|
|
|
|
|
|
.. sectionauthor:: Michael Hudson <mwh@python.net>
|
|
|
|
.. sectionauthor:: Dave Kuhlman <dkuhlman@rexx.com>
|
|
|
|
.. sectionauthor:: Jim Fulton <jim@zope.com>
|
|
|
|
|
|
|
|
|
|
|
|
As mentioned in the last chapter, Python allows the writer of an extension
|
|
|
|
module to define new types that can be manipulated from Python code, much like
|
|
|
|
strings and lists in core Python.
|
|
|
|
|
|
|
|
This is not hard; the code for all extension types follows a pattern, but there
|
|
|
|
are some details that you need to understand before you can get started.
|
|
|
|
|
|
|
|
|
|
|
|
.. _dnt-basics:
|
|
|
|
|
|
|
|
The Basics
|
|
|
|
==========
|
|
|
|
|
|
|
|
The Python runtime sees all Python objects as variables of type
|
2012-02-27 13:18:35 -04:00
|
|
|
:c:type:`PyObject\*`, which serves as a "base type" for all Python objects.
|
|
|
|
:c:type:`PyObject` itself only contains the refcount and a pointer to the
|
|
|
|
object's "type object". This is where the action is; the type object determines
|
|
|
|
which (C) functions get called when, for instance, an attribute gets looked
|
|
|
|
up on an object or it is multiplied by another object. These C functions
|
|
|
|
are called "type methods".
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
So, if you want to define a new object type, you need to create a new type
|
|
|
|
object.
|
|
|
|
|
|
|
|
This sort of thing can only be explained by example, so here's a minimal, but
|
|
|
|
complete, module that defines a new type:
|
|
|
|
|
|
|
|
.. literalinclude:: ../includes/noddy.c
|
|
|
|
|
|
|
|
|
|
|
|
Now that's quite a bit to take in at once, but hopefully bits will seem familiar
|
|
|
|
from the last chapter.
|
|
|
|
|
|
|
|
The first bit that will be new is::
|
|
|
|
|
|
|
|
typedef struct {
|
|
|
|
PyObject_HEAD
|
|
|
|
} noddy_NoddyObject;
|
|
|
|
|
2012-02-27 13:18:35 -04:00
|
|
|
This is what a Noddy object will contain---in this case, nothing more than what
|
2016-08-03 06:58:49 -03:00
|
|
|
every Python object contains---a field called ``ob_base`` of type
|
|
|
|
:c:type:`PyObject`. :c:type:`PyObject` in turn, contains an ``ob_refcnt``
|
|
|
|
field and a pointer to a type object. These can be accessed using the macros
|
|
|
|
:c:macro:`Py_REFCNT` and :c:macro:`Py_TYPE` respectively. These are the fields
|
|
|
|
the :c:macro:`PyObject_HEAD` macro brings in. The reason for the macro is to
|
|
|
|
standardize the layout and to enable special debugging fields in debug builds.
|
|
|
|
|
|
|
|
Note that there is no semicolon after the :c:macro:`PyObject_HEAD` macro;
|
|
|
|
one is included in the macro definition. Be wary of adding one by
|
2012-02-27 13:18:35 -04:00
|
|
|
accident; it's easy to do from habit, and your compiler might not complain,
|
|
|
|
but someone else's probably will! (On Windows, MSVC is known to call this an
|
|
|
|
error and refuse to compile the code.)
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
For contrast, let's take a look at the corresponding definition for standard
|
2007-12-08 14:59:56 -04:00
|
|
|
Python floats::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
typedef struct {
|
|
|
|
PyObject_HEAD
|
2007-12-08 14:59:56 -04:00
|
|
|
double ob_fval;
|
|
|
|
} PyFloatObject;
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
Moving on, we come to the crunch --- the type object. ::
|
|
|
|
|
|
|
|
static PyTypeObject noddy_NoddyType = {
|
2009-02-27 13:11:23 -04:00
|
|
|
PyVarObject_HEAD_INIT(NULL, 0)
|
2008-12-05 11:12:15 -04:00
|
|
|
"noddy.Noddy", /* tp_name */
|
|
|
|
sizeof(noddy_NoddyObject), /* tp_basicsize */
|
|
|
|
0, /* tp_itemsize */
|
|
|
|
0, /* tp_dealloc */
|
|
|
|
0, /* tp_print */
|
|
|
|
0, /* tp_getattr */
|
|
|
|
0, /* tp_setattr */
|
2015-05-21 12:50:30 -03:00
|
|
|
0, /* tp_as_async */
|
2008-12-05 11:12:15 -04:00
|
|
|
0, /* tp_repr */
|
|
|
|
0, /* tp_as_number */
|
|
|
|
0, /* tp_as_sequence */
|
|
|
|
0, /* tp_as_mapping */
|
|
|
|
0, /* tp_hash */
|
|
|
|
0, /* tp_call */
|
|
|
|
0, /* tp_str */
|
|
|
|
0, /* tp_getattro */
|
|
|
|
0, /* tp_setattro */
|
|
|
|
0, /* tp_as_buffer */
|
|
|
|
Py_TPFLAGS_DEFAULT, /* tp_flags */
|
2007-08-15 11:28:22 -03:00
|
|
|
"Noddy objects", /* tp_doc */
|
|
|
|
};
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
Now if you go and look up the definition of :c:type:`PyTypeObject` in
|
2007-08-15 11:28:22 -03:00
|
|
|
:file:`object.h` you'll see that it has many more fields that the definition
|
|
|
|
above. The remaining fields will be filled with zeros by the C compiler, and
|
|
|
|
it's common practice to not specify them explicitly unless you need them.
|
|
|
|
|
|
|
|
This is so important that we're going to pick the top of it apart still
|
|
|
|
further::
|
|
|
|
|
2009-02-27 13:11:23 -04:00
|
|
|
PyVarObject_HEAD_INIT(NULL, 0)
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
This line is a bit of a wart; what we'd like to write is::
|
|
|
|
|
2009-02-27 13:11:23 -04:00
|
|
|
PyVarObject_HEAD_INIT(&PyType_Type, 0)
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
as the type of a type object is "type", but this isn't strictly conforming C and
|
|
|
|
some compilers complain. Fortunately, this member will be filled in for us by
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:func:`PyType_Ready`. ::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
"noddy.Noddy", /* tp_name */
|
|
|
|
|
|
|
|
The name of our type. This will appear in the default textual representation of
|
|
|
|
our objects and in some error messages, for example::
|
|
|
|
|
|
|
|
>>> "" + noddy.new_noddy()
|
|
|
|
Traceback (most recent call last):
|
2017-05-03 22:41:20 -03:00
|
|
|
File "<stdin>", line 1, in <module>
|
2007-08-15 11:28:22 -03:00
|
|
|
TypeError: cannot add type "noddy.Noddy" to string
|
|
|
|
|
|
|
|
Note that the name is a dotted name that includes both the module name and the
|
|
|
|
name of the type within the module. The module in this case is :mod:`noddy` and
|
2016-10-07 17:24:35 -03:00
|
|
|
the type is :class:`Noddy`, so we set the type name to :class:`noddy.Noddy`.
|
|
|
|
One side effect of using an undotted name is that the pydoc documentation tool
|
|
|
|
will not list the new type in the module documentation. ::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
sizeof(noddy_NoddyObject), /* tp_basicsize */
|
|
|
|
|
|
|
|
This is so that Python knows how much memory to allocate when you call
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:func:`PyObject_New`.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
.. note::
|
|
|
|
|
|
|
|
If you want your type to be subclassable from Python, and your type has the same
|
2013-08-01 16:12:45 -03:00
|
|
|
:c:member:`~PyTypeObject.tp_basicsize` as its base type, you may have problems with multiple
|
2007-08-15 11:28:22 -03:00
|
|
|
inheritance. A Python subclass of your type will have to list your type first
|
2013-10-09 07:26:17 -03:00
|
|
|
in its :attr:`~class.__bases__`, or else it will not be able to call your type's
|
2007-08-15 11:28:22 -03:00
|
|
|
:meth:`__new__` method without getting an error. You can avoid this problem by
|
2013-08-01 16:12:45 -03:00
|
|
|
ensuring that your type has a larger value for :c:member:`~PyTypeObject.tp_basicsize` than its
|
2007-08-15 11:28:22 -03:00
|
|
|
base type does. Most of the time, this will be true anyway, because either your
|
|
|
|
base type will be :class:`object`, or else you will be adding data members to
|
|
|
|
your base type, and therefore increasing its size.
|
|
|
|
|
|
|
|
::
|
|
|
|
|
|
|
|
0, /* tp_itemsize */
|
|
|
|
|
|
|
|
This has to do with variable length objects like lists and strings. Ignore this
|
|
|
|
for now.
|
|
|
|
|
|
|
|
Skipping a number of type methods that we don't provide, we set the class flags
|
|
|
|
to :const:`Py_TPFLAGS_DEFAULT`. ::
|
|
|
|
|
2008-12-05 11:12:15 -04:00
|
|
|
Py_TPFLAGS_DEFAULT, /* tp_flags */
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
All types should include this constant in their flags. It enables all of the
|
2013-07-30 14:59:21 -03:00
|
|
|
members defined until at least Python 3.3. If you need further members,
|
|
|
|
you will need to OR the corresponding flags.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
We provide a doc string for the type in :c:member:`~PyTypeObject.tp_doc`. ::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
"Noddy objects", /* tp_doc */
|
|
|
|
|
|
|
|
Now we get into the type methods, the things that make your objects different
|
|
|
|
from the others. We aren't going to implement any of these in this version of
|
|
|
|
the module. We'll expand this example later to have more interesting behavior.
|
|
|
|
|
|
|
|
For now, all we want to be able to do is to create new :class:`Noddy` objects.
|
2013-08-01 16:12:45 -03:00
|
|
|
To enable object creation, we have to provide a :c:member:`~PyTypeObject.tp_new` implementation.
|
2007-08-15 11:28:22 -03:00
|
|
|
In this case, we can just use the default implementation provided by the API
|
2010-10-06 07:11:56 -03:00
|
|
|
function :c:func:`PyType_GenericNew`. We'd like to just assign this to the
|
2013-08-01 16:12:45 -03:00
|
|
|
:c:member:`~PyTypeObject.tp_new` slot, but we can't, for portability sake, On some platforms or
|
2007-08-15 11:28:22 -03:00
|
|
|
compilers, we can't statically initialize a structure member with a function
|
2013-08-01 16:12:45 -03:00
|
|
|
defined in another C module, so, instead, we'll assign the :c:member:`~PyTypeObject.tp_new` slot
|
2007-08-15 11:28:22 -03:00
|
|
|
in the module initialization function just before calling
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:func:`PyType_Ready`::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
noddy_NoddyType.tp_new = PyType_GenericNew;
|
|
|
|
if (PyType_Ready(&noddy_NoddyType) < 0)
|
|
|
|
return;
|
|
|
|
|
|
|
|
All the other type methods are *NULL*, so we'll go over them later --- that's
|
|
|
|
for a later section!
|
|
|
|
|
|
|
|
Everything else in the file should be familiar, except for some code in
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:func:`PyInit_noddy`::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
if (PyType_Ready(&noddy_NoddyType) < 0)
|
|
|
|
return;
|
|
|
|
|
|
|
|
This initializes the :class:`Noddy` type, filing in a number of members,
|
|
|
|
including :attr:`ob_type` that we initially set to *NULL*. ::
|
|
|
|
|
|
|
|
PyModule_AddObject(m, "Noddy", (PyObject *)&noddy_NoddyType);
|
|
|
|
|
|
|
|
This adds the type to the module dictionary. This allows us to create
|
|
|
|
:class:`Noddy` instances by calling the :class:`Noddy` class::
|
|
|
|
|
|
|
|
>>> import noddy
|
|
|
|
>>> mynoddy = noddy.Noddy()
|
|
|
|
|
|
|
|
That's it! All that remains is to build it; put the above code in a file called
|
|
|
|
:file:`noddy.c` and ::
|
|
|
|
|
|
|
|
from distutils.core import setup, Extension
|
|
|
|
setup(name="noddy", version="1.0",
|
|
|
|
ext_modules=[Extension("noddy", ["noddy.c"])])
|
|
|
|
|
2016-07-26 06:18:21 -03:00
|
|
|
in a file called :file:`setup.py`; then typing
|
|
|
|
|
|
|
|
.. code-block:: shell-session
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
$ python setup.py build
|
|
|
|
|
|
|
|
at a shell should produce a file :file:`noddy.so` in a subdirectory; move to
|
|
|
|
that directory and fire up Python --- you should be able to ``import noddy`` and
|
|
|
|
play around with Noddy objects.
|
|
|
|
|
|
|
|
That wasn't so hard, was it?
|
|
|
|
|
|
|
|
Of course, the current Noddy type is pretty uninteresting. It has no data and
|
|
|
|
doesn't do anything. It can't even be subclassed.
|
|
|
|
|
|
|
|
|
|
|
|
Adding data and methods to the Basic example
|
|
|
|
--------------------------------------------
|
|
|
|
|
2012-02-27 13:18:35 -04:00
|
|
|
Let's extend the basic example to add some data and methods. Let's also make
|
2007-08-15 11:28:22 -03:00
|
|
|
the type usable as a base class. We'll create a new module, :mod:`noddy2` that
|
|
|
|
adds these capabilities:
|
|
|
|
|
|
|
|
.. literalinclude:: ../includes/noddy2.c
|
|
|
|
|
|
|
|
|
|
|
|
This version of the module has a number of changes.
|
|
|
|
|
|
|
|
We've added an extra include::
|
|
|
|
|
2010-03-21 07:03:36 -03:00
|
|
|
#include <structmember.h>
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
This include provides declarations that we use to handle attributes, as
|
|
|
|
described a bit later.
|
|
|
|
|
|
|
|
The name of the :class:`Noddy` object structure has been shortened to
|
|
|
|
:class:`Noddy`. The type object name has been shortened to :class:`NoddyType`.
|
|
|
|
|
|
|
|
The :class:`Noddy` type now has three data attributes, *first*, *last*, and
|
|
|
|
*number*. The *first* and *last* variables are Python strings containing first
|
|
|
|
and last names. The *number* attribute is an integer.
|
|
|
|
|
|
|
|
The object structure is updated accordingly::
|
|
|
|
|
|
|
|
typedef struct {
|
|
|
|
PyObject_HEAD
|
|
|
|
PyObject *first;
|
|
|
|
PyObject *last;
|
|
|
|
int number;
|
|
|
|
} Noddy;
|
|
|
|
|
|
|
|
Because we now have data to manage, we have to be more careful about object
|
|
|
|
allocation and deallocation. At a minimum, we need a deallocation method::
|
|
|
|
|
|
|
|
static void
|
|
|
|
Noddy_dealloc(Noddy* self)
|
|
|
|
{
|
|
|
|
Py_XDECREF(self->first);
|
|
|
|
Py_XDECREF(self->last);
|
2008-12-07 10:09:20 -04:00
|
|
|
Py_TYPE(self)->tp_free((PyObject*)self);
|
2007-08-15 11:28:22 -03:00
|
|
|
}
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
which is assigned to the :c:member:`~PyTypeObject.tp_dealloc` member::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
(destructor)Noddy_dealloc, /*tp_dealloc*/
|
|
|
|
|
|
|
|
This method decrements the reference counts of the two Python attributes. We use
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:func:`Py_XDECREF` here because the :attr:`first` and :attr:`last` members
|
2013-08-01 16:12:45 -03:00
|
|
|
could be *NULL*. It then calls the :c:member:`~PyTypeObject.tp_free` member of the object's type
|
2007-08-15 11:28:22 -03:00
|
|
|
to free the object's memory. Note that the object's type might not be
|
|
|
|
:class:`NoddyType`, because the object may be an instance of a subclass.
|
|
|
|
|
|
|
|
We want to make sure that the first and last names are initialized to empty
|
|
|
|
strings, so we provide a new method::
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
Noddy_new(PyTypeObject *type, PyObject *args, PyObject *kwds)
|
|
|
|
{
|
|
|
|
Noddy *self;
|
|
|
|
|
|
|
|
self = (Noddy *)type->tp_alloc(type, 0);
|
|
|
|
if (self != NULL) {
|
2013-03-22 17:43:30 -03:00
|
|
|
self->first = PyUnicode_FromString("");
|
2011-08-12 05:40:39 -03:00
|
|
|
if (self->first == NULL) {
|
2007-08-15 11:28:22 -03:00
|
|
|
Py_DECREF(self);
|
|
|
|
return NULL;
|
2011-08-12 05:40:39 -03:00
|
|
|
}
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2013-03-22 17:43:30 -03:00
|
|
|
self->last = PyUnicode_FromString("");
|
2011-08-12 05:40:39 -03:00
|
|
|
if (self->last == NULL) {
|
2007-08-15 11:28:22 -03:00
|
|
|
Py_DECREF(self);
|
|
|
|
return NULL;
|
2011-08-12 05:40:39 -03:00
|
|
|
}
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
self->number = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
return (PyObject *)self;
|
|
|
|
}
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
and install it in the :c:member:`~PyTypeObject.tp_new` member::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
Noddy_new, /* tp_new */
|
|
|
|
|
|
|
|
The new member is responsible for creating (as opposed to initializing) objects
|
|
|
|
of the type. It is exposed in Python as the :meth:`__new__` method. See the
|
|
|
|
paper titled "Unifying types and classes in Python" for a detailed discussion of
|
|
|
|
the :meth:`__new__` method. One reason to implement a new method is to assure
|
|
|
|
the initial values of instance variables. In this case, we use the new method
|
|
|
|
to make sure that the initial values of the members :attr:`first` and
|
|
|
|
:attr:`last` are not *NULL*. If we didn't care whether the initial values were
|
2010-10-06 07:11:56 -03:00
|
|
|
*NULL*, we could have used :c:func:`PyType_GenericNew` as our new method, as we
|
|
|
|
did before. :c:func:`PyType_GenericNew` initializes all of the instance variable
|
2007-08-15 11:28:22 -03:00
|
|
|
members to *NULL*.
|
|
|
|
|
|
|
|
The new method is a static method that is passed the type being instantiated and
|
|
|
|
any arguments passed when the type was called, and that returns the new object
|
|
|
|
created. New methods always accept positional and keyword arguments, but they
|
|
|
|
often ignore the arguments, leaving the argument handling to initializer
|
|
|
|
methods. Note that if the type supports subclassing, the type passed may not be
|
2013-08-01 16:12:45 -03:00
|
|
|
the type being defined. The new method calls the :c:member:`~PyTypeObject.tp_alloc` slot to
|
|
|
|
allocate memory. We don't fill the :c:member:`~PyTypeObject.tp_alloc` slot ourselves. Rather
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:func:`PyType_Ready` fills it for us by inheriting it from our base class,
|
2007-08-15 11:28:22 -03:00
|
|
|
which is :class:`object` by default. Most types use the default allocation.
|
|
|
|
|
|
|
|
.. note::
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
If you are creating a co-operative :c:member:`~PyTypeObject.tp_new` (one that calls a base type's
|
|
|
|
:c:member:`~PyTypeObject.tp_new` or :meth:`__new__`), you must *not* try to determine what method
|
2007-08-15 11:28:22 -03:00
|
|
|
to call using method resolution order at runtime. Always statically determine
|
2013-08-01 16:12:45 -03:00
|
|
|
what type you are going to call, and call its :c:member:`~PyTypeObject.tp_new` directly, or via
|
2007-08-15 11:28:22 -03:00
|
|
|
``type->tp_base->tp_new``. If you do not do this, Python subclasses of your
|
|
|
|
type that also inherit from other Python-defined classes may not work correctly.
|
|
|
|
(Specifically, you may not be able to create instances of such subclasses
|
|
|
|
without getting a :exc:`TypeError`.)
|
|
|
|
|
|
|
|
We provide an initialization function::
|
|
|
|
|
|
|
|
static int
|
|
|
|
Noddy_init(Noddy *self, PyObject *args, PyObject *kwds)
|
|
|
|
{
|
|
|
|
PyObject *first=NULL, *last=NULL, *tmp;
|
|
|
|
|
|
|
|
static char *kwlist[] = {"first", "last", "number", NULL};
|
|
|
|
|
|
|
|
if (! PyArg_ParseTupleAndKeywords(args, kwds, "|OOi", kwlist,
|
|
|
|
&first, &last,
|
|
|
|
&self->number))
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
if (first) {
|
|
|
|
tmp = self->first;
|
|
|
|
Py_INCREF(first);
|
|
|
|
self->first = first;
|
|
|
|
Py_XDECREF(tmp);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (last) {
|
|
|
|
tmp = self->last;
|
|
|
|
Py_INCREF(last);
|
|
|
|
self->last = last;
|
|
|
|
Py_XDECREF(tmp);
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
by filling the :c:member:`~PyTypeObject.tp_init` slot. ::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
(initproc)Noddy_init, /* tp_init */
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
The :c:member:`~PyTypeObject.tp_init` slot is exposed in Python as the :meth:`__init__` method. It
|
2007-08-15 11:28:22 -03:00
|
|
|
is used to initialize an object after it's created. Unlike the new method, we
|
|
|
|
can't guarantee that the initializer is called. The initializer isn't called
|
|
|
|
when unpickling objects and it can be overridden. Our initializer accepts
|
|
|
|
arguments to provide initial values for our instance. Initializers always accept
|
2015-04-12 22:51:36 -03:00
|
|
|
positional and keyword arguments. Initializers should return either 0 on
|
|
|
|
success or -1 on error.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
Initializers can be called multiple times. Anyone can call the :meth:`__init__`
|
|
|
|
method on our objects. For this reason, we have to be extra careful when
|
|
|
|
assigning the new values. We might be tempted, for example to assign the
|
|
|
|
:attr:`first` member like this::
|
|
|
|
|
|
|
|
if (first) {
|
|
|
|
Py_XDECREF(self->first);
|
|
|
|
Py_INCREF(first);
|
|
|
|
self->first = first;
|
|
|
|
}
|
|
|
|
|
|
|
|
But this would be risky. Our type doesn't restrict the type of the
|
|
|
|
:attr:`first` member, so it could be any kind of object. It could have a
|
|
|
|
destructor that causes code to be executed that tries to access the
|
|
|
|
:attr:`first` member. To be paranoid and protect ourselves against this
|
|
|
|
possibility, we almost always reassign members before decrementing their
|
|
|
|
reference counts. When don't we have to do this?
|
|
|
|
|
|
|
|
* when we absolutely know that the reference count is greater than 1
|
|
|
|
|
|
|
|
* when we know that deallocation of the object [#]_ will not cause any calls
|
|
|
|
back into our type's code
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
* when decrementing a reference count in a :c:member:`~PyTypeObject.tp_dealloc` handler when
|
2007-08-15 11:28:22 -03:00
|
|
|
garbage-collections is not supported [#]_
|
|
|
|
|
2008-03-16 14:29:44 -03:00
|
|
|
We want to expose our instance variables as attributes. There are a
|
2007-08-15 11:28:22 -03:00
|
|
|
number of ways to do that. The simplest way is to define member definitions::
|
|
|
|
|
|
|
|
static PyMemberDef Noddy_members[] = {
|
|
|
|
{"first", T_OBJECT_EX, offsetof(Noddy, first), 0,
|
|
|
|
"first name"},
|
|
|
|
{"last", T_OBJECT_EX, offsetof(Noddy, last), 0,
|
|
|
|
"last name"},
|
|
|
|
{"number", T_INT, offsetof(Noddy, number), 0,
|
|
|
|
"noddy number"},
|
|
|
|
{NULL} /* Sentinel */
|
|
|
|
};
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
and put the definitions in the :c:member:`~PyTypeObject.tp_members` slot::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
Noddy_members, /* tp_members */
|
|
|
|
|
|
|
|
Each member definition has a member name, type, offset, access flags and
|
2010-05-31 22:11:18 -03:00
|
|
|
documentation string. See the :ref:`Generic-Attribute-Management` section below for
|
2007-08-15 11:28:22 -03:00
|
|
|
details.
|
|
|
|
|
|
|
|
A disadvantage of this approach is that it doesn't provide a way to restrict the
|
|
|
|
types of objects that can be assigned to the Python attributes. We expect the
|
|
|
|
first and last names to be strings, but any Python objects can be assigned.
|
|
|
|
Further, the attributes can be deleted, setting the C pointers to *NULL*. Even
|
|
|
|
though we can make sure the members are initialized to non-*NULL* values, the
|
|
|
|
members can be set to *NULL* if the attributes are deleted.
|
|
|
|
|
|
|
|
We define a single method, :meth:`name`, that outputs the objects name as the
|
|
|
|
concatenation of the first and last names. ::
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
Noddy_name(Noddy* self)
|
|
|
|
{
|
|
|
|
if (self->first == NULL) {
|
|
|
|
PyErr_SetString(PyExc_AttributeError, "first");
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (self->last == NULL) {
|
|
|
|
PyErr_SetString(PyExc_AttributeError, "last");
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
2012-02-27 13:18:35 -04:00
|
|
|
return PyUnicode_FromFormat("%S %S", self->first, self->last);
|
2007-08-15 11:28:22 -03:00
|
|
|
}
|
|
|
|
|
|
|
|
The method is implemented as a C function that takes a :class:`Noddy` (or
|
|
|
|
:class:`Noddy` subclass) instance as the first argument. Methods always take an
|
|
|
|
instance as the first argument. Methods often take positional and keyword
|
2012-02-27 13:18:35 -04:00
|
|
|
arguments as well, but in this case we don't take any and don't need to accept
|
2007-08-15 11:28:22 -03:00
|
|
|
a positional argument tuple or keyword argument dictionary. This method is
|
|
|
|
equivalent to the Python method::
|
|
|
|
|
|
|
|
def name(self):
|
|
|
|
return "%s %s" % (self.first, self.last)
|
|
|
|
|
|
|
|
Note that we have to check for the possibility that our :attr:`first` and
|
|
|
|
:attr:`last` members are *NULL*. This is because they can be deleted, in which
|
|
|
|
case they are set to *NULL*. It would be better to prevent deletion of these
|
|
|
|
attributes and to restrict the attribute values to be strings. We'll see how to
|
|
|
|
do that in the next section.
|
|
|
|
|
|
|
|
Now that we've defined the method, we need to create an array of method
|
|
|
|
definitions::
|
|
|
|
|
|
|
|
static PyMethodDef Noddy_methods[] = {
|
|
|
|
{"name", (PyCFunction)Noddy_name, METH_NOARGS,
|
|
|
|
"Return the name, combining the first and last name"
|
|
|
|
},
|
|
|
|
{NULL} /* Sentinel */
|
|
|
|
};
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
and assign them to the :c:member:`~PyTypeObject.tp_methods` slot::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
Noddy_methods, /* tp_methods */
|
|
|
|
|
|
|
|
Note that we used the :const:`METH_NOARGS` flag to indicate that the method is
|
|
|
|
passed no arguments.
|
|
|
|
|
|
|
|
Finally, we'll make our type usable as a base class. We've written our methods
|
|
|
|
carefully so far so that they don't make any assumptions about the type of the
|
|
|
|
object being created or used, so all we need to do is to add the
|
|
|
|
:const:`Py_TPFLAGS_BASETYPE` to our class flag definition::
|
|
|
|
|
|
|
|
Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE, /*tp_flags*/
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
We rename :c:func:`PyInit_noddy` to :c:func:`PyInit_noddy2` and update the module
|
|
|
|
name in the :c:type:`PyModuleDef` struct.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
Finally, we update our :file:`setup.py` file to build the new module::
|
|
|
|
|
|
|
|
from distutils.core import setup, Extension
|
|
|
|
setup(name="noddy", version="1.0",
|
|
|
|
ext_modules=[
|
|
|
|
Extension("noddy", ["noddy.c"]),
|
|
|
|
Extension("noddy2", ["noddy2.c"]),
|
|
|
|
])
|
|
|
|
|
|
|
|
|
|
|
|
Providing finer control over data attributes
|
|
|
|
--------------------------------------------
|
|
|
|
|
|
|
|
In this section, we'll provide finer control over how the :attr:`first` and
|
|
|
|
:attr:`last` attributes are set in the :class:`Noddy` example. In the previous
|
|
|
|
version of our module, the instance variables :attr:`first` and :attr:`last`
|
|
|
|
could be set to non-string values or even deleted. We want to make sure that
|
|
|
|
these attributes always contain strings.
|
|
|
|
|
|
|
|
.. literalinclude:: ../includes/noddy3.c
|
|
|
|
|
|
|
|
|
|
|
|
To provide greater control, over the :attr:`first` and :attr:`last` attributes,
|
|
|
|
we'll use custom getter and setter functions. Here are the functions for
|
|
|
|
getting and setting the :attr:`first` attribute::
|
|
|
|
|
|
|
|
Noddy_getfirst(Noddy *self, void *closure)
|
|
|
|
{
|
|
|
|
Py_INCREF(self->first);
|
|
|
|
return self->first;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
Noddy_setfirst(Noddy *self, PyObject *value, void *closure)
|
|
|
|
{
|
|
|
|
if (value == NULL) {
|
|
|
|
PyErr_SetString(PyExc_TypeError, "Cannot delete the first attribute");
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2013-03-22 17:43:30 -03:00
|
|
|
if (! PyUnicode_Check(value)) {
|
2007-08-15 11:28:22 -03:00
|
|
|
PyErr_SetString(PyExc_TypeError,
|
2013-03-22 17:43:30 -03:00
|
|
|
"The first attribute value must be a str");
|
2007-08-15 11:28:22 -03:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
|
|
|
Py_DECREF(self->first);
|
|
|
|
Py_INCREF(value);
|
|
|
|
self->first = value;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
The getter function is passed a :class:`Noddy` object and a "closure", which is
|
|
|
|
void pointer. In this case, the closure is ignored. (The closure supports an
|
|
|
|
advanced usage in which definition data is passed to the getter and setter. This
|
|
|
|
could, for example, be used to allow a single set of getter and setter functions
|
|
|
|
that decide the attribute to get or set based on data in the closure.)
|
|
|
|
|
|
|
|
The setter function is passed the :class:`Noddy` object, the new value, and the
|
|
|
|
closure. The new value may be *NULL*, in which case the attribute is being
|
|
|
|
deleted. In our setter, we raise an error if the attribute is deleted or if the
|
|
|
|
attribute value is not a string.
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
We create an array of :c:type:`PyGetSetDef` structures::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
static PyGetSetDef Noddy_getseters[] = {
|
|
|
|
{"first",
|
|
|
|
(getter)Noddy_getfirst, (setter)Noddy_setfirst,
|
|
|
|
"first name",
|
|
|
|
NULL},
|
|
|
|
{"last",
|
|
|
|
(getter)Noddy_getlast, (setter)Noddy_setlast,
|
|
|
|
"last name",
|
|
|
|
NULL},
|
|
|
|
{NULL} /* Sentinel */
|
|
|
|
};
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
and register it in the :c:member:`~PyTypeObject.tp_getset` slot::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
Noddy_getseters, /* tp_getset */
|
|
|
|
|
2008-03-16 14:29:44 -03:00
|
|
|
to register our attribute getters and setters.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
The last item in a :c:type:`PyGetSetDef` structure is the closure mentioned
|
2007-08-15 11:28:22 -03:00
|
|
|
above. In this case, we aren't using the closure, so we just pass *NULL*.
|
|
|
|
|
|
|
|
We also remove the member definitions for these attributes::
|
|
|
|
|
|
|
|
static PyMemberDef Noddy_members[] = {
|
|
|
|
{"number", T_INT, offsetof(Noddy, number), 0,
|
|
|
|
"noddy number"},
|
|
|
|
{NULL} /* Sentinel */
|
|
|
|
};
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
We also need to update the :c:member:`~PyTypeObject.tp_init` handler to only allow strings [#]_ to
|
2007-08-15 11:28:22 -03:00
|
|
|
be passed::
|
|
|
|
|
|
|
|
static int
|
|
|
|
Noddy_init(Noddy *self, PyObject *args, PyObject *kwds)
|
|
|
|
{
|
|
|
|
PyObject *first=NULL, *last=NULL, *tmp;
|
|
|
|
|
|
|
|
static char *kwlist[] = {"first", "last", "number", NULL};
|
|
|
|
|
|
|
|
if (! PyArg_ParseTupleAndKeywords(args, kwds, "|SSi", kwlist,
|
|
|
|
&first, &last,
|
|
|
|
&self->number))
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
if (first) {
|
|
|
|
tmp = self->first;
|
|
|
|
Py_INCREF(first);
|
|
|
|
self->first = first;
|
|
|
|
Py_DECREF(tmp);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (last) {
|
|
|
|
tmp = self->last;
|
|
|
|
Py_INCREF(last);
|
|
|
|
self->last = last;
|
|
|
|
Py_DECREF(tmp);
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
With these changes, we can assure that the :attr:`first` and :attr:`last`
|
|
|
|
members are never *NULL* so we can remove checks for *NULL* values in almost all
|
2010-10-06 07:11:56 -03:00
|
|
|
cases. This means that most of the :c:func:`Py_XDECREF` calls can be converted to
|
|
|
|
:c:func:`Py_DECREF` calls. The only place we can't change these calls is in the
|
2007-08-15 11:28:22 -03:00
|
|
|
deallocator, where there is the possibility that the initialization of these
|
|
|
|
members failed in the constructor.
|
|
|
|
|
|
|
|
We also rename the module initialization function and module name in the
|
|
|
|
initialization function, as we did before, and we add an extra definition to the
|
|
|
|
:file:`setup.py` file.
|
|
|
|
|
|
|
|
|
|
|
|
Supporting cyclic garbage collection
|
|
|
|
------------------------------------
|
|
|
|
|
|
|
|
Python has a cyclic-garbage collector that can identify unneeded objects even
|
|
|
|
when their reference counts are not zero. This can happen when objects are
|
|
|
|
involved in cycles. For example, consider::
|
|
|
|
|
|
|
|
>>> l = []
|
|
|
|
>>> l.append(l)
|
|
|
|
>>> del l
|
|
|
|
|
|
|
|
In this example, we create a list that contains itself. When we delete it, it
|
|
|
|
still has a reference from itself. Its reference count doesn't drop to zero.
|
|
|
|
Fortunately, Python's cyclic-garbage collector will eventually figure out that
|
|
|
|
the list is garbage and free it.
|
|
|
|
|
|
|
|
In the second version of the :class:`Noddy` example, we allowed any kind of
|
|
|
|
object to be stored in the :attr:`first` or :attr:`last` attributes. [#]_ This
|
|
|
|
means that :class:`Noddy` objects can participate in cycles::
|
|
|
|
|
|
|
|
>>> import noddy2
|
|
|
|
>>> n = noddy2.Noddy()
|
|
|
|
>>> l = [n]
|
|
|
|
>>> n.first = l
|
|
|
|
|
|
|
|
This is pretty silly, but it gives us an excuse to add support for the
|
|
|
|
cyclic-garbage collector to the :class:`Noddy` example. To support cyclic
|
|
|
|
garbage collection, types need to fill two slots and set a class flag that
|
|
|
|
enables these slots:
|
|
|
|
|
|
|
|
.. literalinclude:: ../includes/noddy4.c
|
|
|
|
|
|
|
|
|
|
|
|
The traversal method provides access to subobjects that could participate in
|
|
|
|
cycles::
|
|
|
|
|
|
|
|
static int
|
|
|
|
Noddy_traverse(Noddy *self, visitproc visit, void *arg)
|
|
|
|
{
|
|
|
|
int vret;
|
|
|
|
|
|
|
|
if (self->first) {
|
|
|
|
vret = visit(self->first, arg);
|
|
|
|
if (vret != 0)
|
|
|
|
return vret;
|
|
|
|
}
|
|
|
|
if (self->last) {
|
|
|
|
vret = visit(self->last, arg);
|
|
|
|
if (vret != 0)
|
|
|
|
return vret;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
For each subobject that can participate in cycles, we need to call the
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:func:`visit` function, which is passed to the traversal method. The
|
|
|
|
:c:func:`visit` function takes as arguments the subobject and the extra argument
|
2007-08-15 11:28:22 -03:00
|
|
|
*arg* passed to the traversal method. It returns an integer value that must be
|
|
|
|
returned if it is non-zero.
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
Python provides a :c:func:`Py_VISIT` macro that automates calling visit
|
|
|
|
functions. With :c:func:`Py_VISIT`, :c:func:`Noddy_traverse` can be simplified::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
static int
|
|
|
|
Noddy_traverse(Noddy *self, visitproc visit, void *arg)
|
|
|
|
{
|
|
|
|
Py_VISIT(self->first);
|
|
|
|
Py_VISIT(self->last);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
.. note::
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
Note that the :c:member:`~PyTypeObject.tp_traverse` implementation must name its arguments exactly
|
2010-10-06 07:11:56 -03:00
|
|
|
*visit* and *arg* in order to use :c:func:`Py_VISIT`. This is to encourage
|
2007-08-15 11:28:22 -03:00
|
|
|
uniformity across these boring implementations.
|
|
|
|
|
|
|
|
We also need to provide a method for clearing any subobjects that can
|
2017-09-04 00:31:09 -03:00
|
|
|
participate in cycles.
|
|
|
|
|
|
|
|
::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
static int
|
|
|
|
Noddy_clear(Noddy *self)
|
|
|
|
{
|
|
|
|
PyObject *tmp;
|
|
|
|
|
|
|
|
tmp = self->first;
|
|
|
|
self->first = NULL;
|
|
|
|
Py_XDECREF(tmp);
|
|
|
|
|
|
|
|
tmp = self->last;
|
|
|
|
self->last = NULL;
|
|
|
|
Py_XDECREF(tmp);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
Notice the use of a temporary variable in :c:func:`Noddy_clear`. We use the
|
2007-08-15 11:28:22 -03:00
|
|
|
temporary variable so that we can set each member to *NULL* before decrementing
|
|
|
|
its reference count. We do this because, as was discussed earlier, if the
|
|
|
|
reference count drops to zero, we might cause code to run that calls back into
|
|
|
|
the object. In addition, because we now support garbage collection, we also
|
|
|
|
have to worry about code being run that triggers garbage collection. If garbage
|
2013-08-01 16:12:45 -03:00
|
|
|
collection is run, our :c:member:`~PyTypeObject.tp_traverse` handler could get called. We can't
|
2010-10-06 07:11:56 -03:00
|
|
|
take a chance of having :c:func:`Noddy_traverse` called when a member's reference
|
2007-08-15 11:28:22 -03:00
|
|
|
count has dropped to zero and its value hasn't been set to *NULL*.
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
Python provides a :c:func:`Py_CLEAR` that automates the careful decrementing of
|
|
|
|
reference counts. With :c:func:`Py_CLEAR`, the :c:func:`Noddy_clear` function can
|
2008-05-12 15:05:20 -03:00
|
|
|
be simplified::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
static int
|
|
|
|
Noddy_clear(Noddy *self)
|
|
|
|
{
|
|
|
|
Py_CLEAR(self->first);
|
|
|
|
Py_CLEAR(self->last);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2017-09-04 00:31:09 -03:00
|
|
|
Note that :c:func:`Noddy_dealloc` may call arbitrary functions through
|
|
|
|
``__del__`` method or weakref callback. It means circular GC can be
|
|
|
|
triggered inside the function. Since GC assumes reference count is not zero,
|
|
|
|
we need to untrack the object from GC by calling :c:func:`PyObject_GC_UnTrack`
|
|
|
|
before clearing members. Here is reimplemented deallocator which uses
|
|
|
|
:c:func:`PyObject_GC_UnTrack` and :c:func:`Noddy_clear`.
|
|
|
|
|
|
|
|
::
|
|
|
|
|
|
|
|
static void
|
|
|
|
Noddy_dealloc(Noddy* self)
|
|
|
|
{
|
|
|
|
PyObject_GC_UnTrack(self);
|
|
|
|
Noddy_clear(self);
|
|
|
|
Py_TYPE(self)->tp_free((PyObject*)self);
|
|
|
|
}
|
|
|
|
|
2007-08-15 11:28:22 -03:00
|
|
|
Finally, we add the :const:`Py_TPFLAGS_HAVE_GC` flag to the class flags::
|
|
|
|
|
2008-12-05 11:12:15 -04:00
|
|
|
Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE | Py_TPFLAGS_HAVE_GC, /* tp_flags */
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
That's pretty much it. If we had written custom :c:member:`~PyTypeObject.tp_alloc` or
|
|
|
|
:c:member:`~PyTypeObject.tp_free` slots, we'd need to modify them for cyclic-garbage collection.
|
2007-08-15 11:28:22 -03:00
|
|
|
Most extensions will use the versions automatically provided.
|
|
|
|
|
|
|
|
|
|
|
|
Subclassing other types
|
|
|
|
-----------------------
|
|
|
|
|
|
|
|
It is possible to create new extension types that are derived from existing
|
|
|
|
types. It is easiest to inherit from the built in types, since an extension can
|
|
|
|
easily use the :class:`PyTypeObject` it needs. It can be difficult to share
|
|
|
|
these :class:`PyTypeObject` structures between extension modules.
|
|
|
|
|
|
|
|
In this example we will create a :class:`Shoddy` type that inherits from the
|
2009-07-26 11:54:51 -03:00
|
|
|
built-in :class:`list` type. The new type will be completely compatible with
|
2007-08-15 11:28:22 -03:00
|
|
|
regular lists, but will have an additional :meth:`increment` method that
|
|
|
|
increases an internal counter. ::
|
|
|
|
|
|
|
|
>>> import shoddy
|
|
|
|
>>> s = shoddy.Shoddy(range(3))
|
|
|
|
>>> s.extend(s)
|
2007-09-04 04:15:32 -03:00
|
|
|
>>> print(len(s))
|
2007-08-15 11:28:22 -03:00
|
|
|
6
|
2007-09-04 04:15:32 -03:00
|
|
|
>>> print(s.increment())
|
2007-08-15 11:28:22 -03:00
|
|
|
1
|
2007-09-04 04:15:32 -03:00
|
|
|
>>> print(s.increment())
|
2007-08-15 11:28:22 -03:00
|
|
|
2
|
|
|
|
|
|
|
|
.. literalinclude:: ../includes/shoddy.c
|
|
|
|
|
|
|
|
|
|
|
|
As you can see, the source code closely resembles the :class:`Noddy` examples in
|
|
|
|
previous sections. We will break down the main differences between them. ::
|
|
|
|
|
|
|
|
typedef struct {
|
2009-01-03 17:26:05 -04:00
|
|
|
PyListObject list;
|
|
|
|
int state;
|
2007-08-15 11:28:22 -03:00
|
|
|
} Shoddy;
|
|
|
|
|
|
|
|
The primary difference for derived type objects is that the base type's object
|
|
|
|
structure must be the first value. The base type will already include the
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:func:`PyObject_HEAD` at the beginning of its structure.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
When a Python object is a :class:`Shoddy` instance, its *PyObject\** pointer can
|
|
|
|
be safely cast to both *PyListObject\** and *Shoddy\**. ::
|
|
|
|
|
|
|
|
static int
|
|
|
|
Shoddy_init(Shoddy *self, PyObject *args, PyObject *kwds)
|
|
|
|
{
|
2009-01-03 17:26:05 -04:00
|
|
|
if (PyList_Type.tp_init((PyObject *)self, args, kwds) < 0)
|
|
|
|
return -1;
|
|
|
|
self->state = 0;
|
|
|
|
return 0;
|
2007-08-15 11:28:22 -03:00
|
|
|
}
|
|
|
|
|
|
|
|
In the :attr:`__init__` method for our type, we can see how to call through to
|
|
|
|
the :attr:`__init__` method of the base type.
|
|
|
|
|
|
|
|
This pattern is important when writing a type with custom :attr:`new` and
|
|
|
|
:attr:`dealloc` methods. The :attr:`new` method should not actually create the
|
2013-08-01 16:12:45 -03:00
|
|
|
memory for the object with :c:member:`~PyTypeObject.tp_alloc`, that will be handled by the base
|
|
|
|
class when calling its :c:member:`~PyTypeObject.tp_new`.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
When filling out the :c:func:`PyTypeObject` for the :class:`Shoddy` type, you see
|
|
|
|
a slot for :c:func:`tp_base`. Due to cross platform compiler issues, you can't
|
|
|
|
fill that field directly with the :c:func:`PyList_Type`; it can be done later in
|
|
|
|
the module's :c:func:`init` function. ::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
PyMODINIT_FUNC
|
2008-12-05 11:12:15 -04:00
|
|
|
PyInit_shoddy(void)
|
2007-08-15 11:28:22 -03:00
|
|
|
{
|
2009-01-03 17:26:05 -04:00
|
|
|
PyObject *m;
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2009-01-03 17:26:05 -04:00
|
|
|
ShoddyType.tp_base = &PyList_Type;
|
|
|
|
if (PyType_Ready(&ShoddyType) < 0)
|
|
|
|
return NULL;
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2009-01-03 17:26:05 -04:00
|
|
|
m = PyModule_Create(&shoddymodule);
|
|
|
|
if (m == NULL)
|
|
|
|
return NULL;
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2009-01-03 17:26:05 -04:00
|
|
|
Py_INCREF(&ShoddyType);
|
|
|
|
PyModule_AddObject(m, "Shoddy", (PyObject *) &ShoddyType);
|
2009-03-31 12:52:41 -03:00
|
|
|
return m;
|
2007-08-15 11:28:22 -03:00
|
|
|
}
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
Before calling :c:func:`PyType_Ready`, the type structure must have the
|
2013-08-01 16:12:45 -03:00
|
|
|
:c:member:`~PyTypeObject.tp_base` slot filled in. When we are deriving a new type, it is not
|
|
|
|
necessary to fill out the :c:member:`~PyTypeObject.tp_alloc` slot with :c:func:`PyType_GenericNew`
|
2007-08-15 11:28:22 -03:00
|
|
|
-- the allocate function from the base type will be inherited.
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
After that, calling :c:func:`PyType_Ready` and adding the type object to the
|
2007-08-15 11:28:22 -03:00
|
|
|
module is the same as with the basic :class:`Noddy` examples.
|
|
|
|
|
|
|
|
|
|
|
|
.. _dnt-type-methods:
|
|
|
|
|
|
|
|
Type Methods
|
|
|
|
============
|
|
|
|
|
|
|
|
This section aims to give a quick fly-by on the various type methods you can
|
|
|
|
implement and what they do.
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
Here is the definition of :c:type:`PyTypeObject`, with some fields only used in
|
2007-08-15 11:28:22 -03:00
|
|
|
debug builds omitted:
|
|
|
|
|
|
|
|
.. literalinclude:: ../includes/typestruct.h
|
|
|
|
|
|
|
|
|
|
|
|
Now that's a *lot* of methods. Don't worry too much though - if you have a type
|
|
|
|
you want to define, the chances are very good that you will only implement a
|
|
|
|
handful of these.
|
|
|
|
|
|
|
|
As you probably expect by now, we're going to go over this and give more
|
|
|
|
information about the various handlers. We won't go in the order they are
|
|
|
|
defined in the structure, because there is a lot of historical baggage that
|
|
|
|
impacts the ordering of the fields; be sure your type initialization keeps the
|
|
|
|
fields in the right order! It's often easiest to find an example that includes
|
|
|
|
all the fields you need (even if they're initialized to ``0``) and then change
|
|
|
|
the values to suit your new type. ::
|
|
|
|
|
2015-08-25 02:06:39 -03:00
|
|
|
const char *tp_name; /* For printing */
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
The name of the type - as mentioned in the last section, this will appear in
|
|
|
|
various places, almost entirely for diagnostic purposes. Try to choose something
|
|
|
|
that will be helpful in such a situation! ::
|
|
|
|
|
2015-08-25 02:06:39 -03:00
|
|
|
Py_ssize_t tp_basicsize, tp_itemsize; /* For allocation */
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
These fields tell the runtime how much memory to allocate when new objects of
|
|
|
|
this type are created. Python has some built-in support for variable length
|
2013-08-01 16:12:45 -03:00
|
|
|
structures (think: strings, lists) which is where the :c:member:`~PyTypeObject.tp_itemsize` field
|
2007-08-15 11:28:22 -03:00
|
|
|
comes in. This will be dealt with later. ::
|
|
|
|
|
2015-08-25 02:06:39 -03:00
|
|
|
const char *tp_doc;
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
Here you can put a string (or its address) that you want returned when the
|
|
|
|
Python script references ``obj.__doc__`` to retrieve the doc string.
|
|
|
|
|
|
|
|
Now we come to the basic type methods---the ones most extension types will
|
|
|
|
implement.
|
|
|
|
|
|
|
|
|
|
|
|
Finalization and De-allocation
|
|
|
|
------------------------------
|
|
|
|
|
|
|
|
.. index::
|
|
|
|
single: object; deallocation
|
|
|
|
single: deallocation, object
|
|
|
|
single: object; finalization
|
|
|
|
single: finalization, of objects
|
|
|
|
|
|
|
|
::
|
|
|
|
|
|
|
|
destructor tp_dealloc;
|
|
|
|
|
|
|
|
This function is called when the reference count of the instance of your type is
|
|
|
|
reduced to zero and the Python interpreter wants to reclaim it. If your type
|
2013-07-30 14:59:21 -03:00
|
|
|
has memory to free or other clean-up to perform, you can put it here. The
|
|
|
|
object itself needs to be freed here as well. Here is an example of this
|
|
|
|
function::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
static void
|
|
|
|
newdatatype_dealloc(newdatatypeobject * obj)
|
|
|
|
{
|
|
|
|
free(obj->obj_UnderlyingDatatypePtr);
|
2008-12-07 10:09:20 -04:00
|
|
|
Py_TYPE(obj)->tp_free(obj);
|
2007-08-15 11:28:22 -03:00
|
|
|
}
|
|
|
|
|
|
|
|
.. index::
|
|
|
|
single: PyErr_Fetch()
|
|
|
|
single: PyErr_Restore()
|
|
|
|
|
|
|
|
One important requirement of the deallocator function is that it leaves any
|
|
|
|
pending exceptions alone. This is important since deallocators are frequently
|
|
|
|
called as the interpreter unwinds the Python stack; when the stack is unwound
|
|
|
|
due to an exception (rather than normal returns), nothing is done to protect the
|
|
|
|
deallocators from seeing that an exception has already been set. Any actions
|
|
|
|
which a deallocator performs which may cause additional Python code to be
|
|
|
|
executed may detect that an exception has been set. This can lead to misleading
|
|
|
|
errors from the interpreter. The proper way to protect against this is to save
|
|
|
|
a pending exception before performing the unsafe action, and restoring it when
|
2010-10-06 07:11:56 -03:00
|
|
|
done. This can be done using the :c:func:`PyErr_Fetch` and
|
|
|
|
:c:func:`PyErr_Restore` functions::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
static void
|
|
|
|
my_dealloc(PyObject *obj)
|
|
|
|
{
|
|
|
|
MyObject *self = (MyObject *) obj;
|
|
|
|
PyObject *cbresult;
|
|
|
|
|
|
|
|
if (self->my_callback != NULL) {
|
|
|
|
PyObject *err_type, *err_value, *err_traceback;
|
|
|
|
|
2013-07-30 15:09:03 -03:00
|
|
|
/* This saves the current exception state */
|
|
|
|
PyErr_Fetch(&err_type, &err_value, &err_traceback);
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
cbresult = PyObject_CallObject(self->my_callback, NULL);
|
|
|
|
if (cbresult == NULL)
|
|
|
|
PyErr_WriteUnraisable(self->my_callback);
|
|
|
|
else
|
|
|
|
Py_DECREF(cbresult);
|
|
|
|
|
2013-07-30 15:09:03 -03:00
|
|
|
/* This restores the saved exception state */
|
|
|
|
PyErr_Restore(err_type, err_value, err_traceback);
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
Py_DECREF(self->my_callback);
|
|
|
|
}
|
2008-12-07 10:09:20 -04:00
|
|
|
Py_TYPE(obj)->tp_free((PyObject*)self);
|
2007-08-15 11:28:22 -03:00
|
|
|
}
|
|
|
|
|
2013-07-30 14:59:21 -03:00
|
|
|
.. note::
|
|
|
|
There are limitations to what you can safely do in a deallocator function.
|
2013-08-01 16:14:43 -03:00
|
|
|
First, if your type supports garbage collection (using :c:member:`~PyTypeObject.tp_traverse`
|
|
|
|
and/or :c:member:`~PyTypeObject.tp_clear`), some of the object's members can have been
|
|
|
|
cleared or finalized by the time :c:member:`~PyTypeObject.tp_dealloc` is called. Second, in
|
|
|
|
:c:member:`~PyTypeObject.tp_dealloc`, your object is in an unstable state: its reference
|
2013-07-30 14:59:21 -03:00
|
|
|
count is equal to zero. Any call to a non-trivial object or API (as in the
|
2013-08-01 16:14:43 -03:00
|
|
|
example above) might end up calling :c:member:`~PyTypeObject.tp_dealloc` again, causing a
|
2013-07-30 14:59:21 -03:00
|
|
|
double free and a crash.
|
|
|
|
|
|
|
|
Starting with Python 3.4, it is recommended not to put any complex
|
2013-08-01 16:14:43 -03:00
|
|
|
finalization code in :c:member:`~PyTypeObject.tp_dealloc`, and instead use the new
|
2013-07-30 14:59:21 -03:00
|
|
|
:c:member:`~PyTypeObject.tp_finalize` type method.
|
|
|
|
|
|
|
|
.. seealso::
|
|
|
|
:pep:`442` explains the new finalization scheme.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
.. index::
|
2012-11-28 05:38:40 -04:00
|
|
|
single: string; object representation
|
2007-08-15 11:28:22 -03:00
|
|
|
builtin: repr
|
2012-11-28 05:38:40 -04:00
|
|
|
|
|
|
|
Object Presentation
|
|
|
|
-------------------
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
In Python, there are two ways to generate a textual representation of an object:
|
|
|
|
the :func:`repr` function, and the :func:`str` function. (The :func:`print`
|
|
|
|
function just calls :func:`str`.) These handlers are both optional.
|
|
|
|
|
|
|
|
::
|
|
|
|
|
|
|
|
reprfunc tp_repr;
|
|
|
|
reprfunc tp_str;
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
The :c:member:`~PyTypeObject.tp_repr` handler should return a string object containing a
|
2007-08-15 11:28:22 -03:00
|
|
|
representation of the instance for which it is called. Here is a simple
|
|
|
|
example::
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
newdatatype_repr(newdatatypeobject * obj)
|
|
|
|
{
|
2013-03-22 17:43:30 -03:00
|
|
|
return PyUnicode_FromFormat("Repr-ified_newdatatype{{size:\%d}}",
|
|
|
|
obj->obj_UnderlyingDatatypePtr->size);
|
2007-08-15 11:28:22 -03:00
|
|
|
}
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
If no :c:member:`~PyTypeObject.tp_repr` handler is specified, the interpreter will supply a
|
|
|
|
representation that uses the type's :c:member:`~PyTypeObject.tp_name` and a uniquely-identifying
|
2007-08-15 11:28:22 -03:00
|
|
|
value for the object.
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
The :c:member:`~PyTypeObject.tp_str` handler is to :func:`str` what the :c:member:`~PyTypeObject.tp_repr` handler
|
2007-08-15 11:28:22 -03:00
|
|
|
described above is to :func:`repr`; that is, it is called when Python code calls
|
|
|
|
:func:`str` on an instance of your object. Its implementation is very similar
|
2013-08-01 16:12:45 -03:00
|
|
|
to the :c:member:`~PyTypeObject.tp_repr` function, but the resulting string is intended for human
|
|
|
|
consumption. If :c:member:`~PyTypeObject.tp_str` is not specified, the :c:member:`~PyTypeObject.tp_repr` handler is
|
2007-08-15 11:28:22 -03:00
|
|
|
used instead.
|
|
|
|
|
|
|
|
Here is a simple example::
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
newdatatype_str(newdatatypeobject * obj)
|
|
|
|
{
|
2013-03-22 17:43:30 -03:00
|
|
|
return PyUnicode_FromFormat("Stringified_newdatatype{{size:\%d}}",
|
|
|
|
obj->obj_UnderlyingDatatypePtr->size);
|
2007-08-15 11:28:22 -03:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Attribute Management
|
|
|
|
--------------------
|
|
|
|
|
|
|
|
For every object which can support attributes, the corresponding type must
|
|
|
|
provide the functions that control how the attributes are resolved. There needs
|
|
|
|
to be a function which can retrieve attributes (if any are defined), and another
|
|
|
|
to set attributes (if setting attributes is allowed). Removing an attribute is
|
|
|
|
a special case, for which the new value passed to the handler is *NULL*.
|
|
|
|
|
|
|
|
Python supports two pairs of attribute handlers; a type that supports attributes
|
|
|
|
only needs to implement the functions for one pair. The difference is that one
|
2010-10-06 07:11:56 -03:00
|
|
|
pair takes the name of the attribute as a :c:type:`char\*`, while the other
|
|
|
|
accepts a :c:type:`PyObject\*`. Each type can use whichever pair makes more
|
2007-08-15 11:28:22 -03:00
|
|
|
sense for the implementation's convenience. ::
|
|
|
|
|
|
|
|
getattrfunc tp_getattr; /* char * version */
|
|
|
|
setattrfunc tp_setattr;
|
|
|
|
/* ... */
|
2008-07-02 19:59:48 -03:00
|
|
|
getattrofunc tp_getattro; /* PyObject * version */
|
|
|
|
setattrofunc tp_setattro;
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
If accessing attributes of an object is always a simple operation (this will be
|
|
|
|
explained shortly), there are generic implementations which can be used to
|
2010-10-06 07:11:56 -03:00
|
|
|
provide the :c:type:`PyObject\*` version of the attribute management functions.
|
2007-08-15 11:28:22 -03:00
|
|
|
The actual need for type-specific attribute handlers almost completely
|
|
|
|
disappeared starting with Python 2.2, though there are many examples which have
|
|
|
|
not been updated to use some of the new generic mechanism that is available.
|
|
|
|
|
|
|
|
|
2010-05-31 22:11:18 -03:00
|
|
|
.. _generic-attribute-management:
|
|
|
|
|
2007-08-15 11:28:22 -03:00
|
|
|
Generic Attribute Management
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
Most extension types only use *simple* attributes. So, what makes the
|
|
|
|
attributes simple? There are only a couple of conditions that must be met:
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
#. The name of the attributes must be known when :c:func:`PyType_Ready` is
|
2007-08-15 11:28:22 -03:00
|
|
|
called.
|
|
|
|
|
|
|
|
#. No special processing is needed to record that an attribute was looked up or
|
|
|
|
set, nor do actions need to be taken based on the value.
|
|
|
|
|
|
|
|
Note that this list does not place any restrictions on the values of the
|
|
|
|
attributes, when the values are computed, or how relevant data is stored.
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
When :c:func:`PyType_Ready` is called, it uses three tables referenced by the
|
#1370: Finish the merge r58749, log below, by resolving all conflicts in Doc/.
Merged revisions 58221-58741 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk
........
r58221 | georg.brandl | 2007-09-20 10:57:59 -0700 (Thu, 20 Sep 2007) | 2 lines
Patch #1181: add os.environ.clear() method.
........
r58225 | sean.reifschneider | 2007-09-20 23:33:28 -0700 (Thu, 20 Sep 2007) | 3 lines
Issue1704287: "make install" fails unless you do "make" first. Make
oldsharedmods and sharedmods in "libinstall".
........
r58232 | guido.van.rossum | 2007-09-22 13:18:03 -0700 (Sat, 22 Sep 2007) | 4 lines
Patch # 188 by Philip Jenvey.
Make tell() mark CRLF as a newline.
With unit test.
........
r58242 | georg.brandl | 2007-09-24 10:55:47 -0700 (Mon, 24 Sep 2007) | 2 lines
Fix typo and double word.
........
r58245 | georg.brandl | 2007-09-24 10:59:28 -0700 (Mon, 24 Sep 2007) | 2 lines
#1196: document default radix for int().
........
r58247 | georg.brandl | 2007-09-24 11:08:24 -0700 (Mon, 24 Sep 2007) | 2 lines
#1177: accept 2xx responses for https too, not only http.
........
r58249 | andrew.kuchling | 2007-09-24 16:45:51 -0700 (Mon, 24 Sep 2007) | 1 line
Remove stray odd character; grammar fix
........
r58250 | andrew.kuchling | 2007-09-24 16:46:28 -0700 (Mon, 24 Sep 2007) | 1 line
Typo fix
........
r58251 | andrew.kuchling | 2007-09-24 17:09:42 -0700 (Mon, 24 Sep 2007) | 1 line
Add various items
........
r58268 | vinay.sajip | 2007-09-26 22:34:45 -0700 (Wed, 26 Sep 2007) | 1 line
Change to flush and close logic to fix #1760556.
........
r58269 | vinay.sajip | 2007-09-26 22:38:51 -0700 (Wed, 26 Sep 2007) | 1 line
Change to basicConfig() to fix #1021.
........
r58270 | georg.brandl | 2007-09-26 23:26:58 -0700 (Wed, 26 Sep 2007) | 2 lines
#1208: document match object's boolean value.
........
r58271 | vinay.sajip | 2007-09-26 23:56:13 -0700 (Wed, 26 Sep 2007) | 1 line
Minor date change.
........
r58272 | vinay.sajip | 2007-09-27 00:35:10 -0700 (Thu, 27 Sep 2007) | 1 line
Change to LogRecord.__init__() to fix #1206. Note that archaic use of type(x) == types.DictType is because of keeping 1.5.2 compatibility. While this is much less relevant these days, there probably needs to be a separate commit for removing all archaic constructs at the same time.
........
r58288 | brett.cannon | 2007-09-30 12:45:10 -0700 (Sun, 30 Sep 2007) | 9 lines
tuple.__repr__ did not consider a reference loop as it is not possible from
Python code; but it is possible from C. object.__str__ had the issue of not
expecting a type to doing something within it's tp_str implementation that
could trigger an infinite recursion, but it could in C code.. Both found
thanks to BaseException and how it handles its repr.
Closes issue #1686386. Thanks to Thomas Herve for taking an initial stab at
coming up with a solution.
........
r58289 | brett.cannon | 2007-09-30 13:37:19 -0700 (Sun, 30 Sep 2007) | 3 lines
Fix error introduced by r58288; if a tuple is length 0 return its repr and
don't worry about any self-referring tuples.
........
r58294 | facundo.batista | 2007-10-02 10:01:24 -0700 (Tue, 02 Oct 2007) | 11 lines
Made the various is_* operations return booleans. This was discussed
with Cawlishaw by mail, and he basically confirmed that to these is_*
operations, there's no need to return Decimal(0) and Decimal(1) if
the language supports the False and True booleans.
Also added a few tests for the these functions in extra.decTest, since
they are mostly untested (apart from the doctests).
Thanks Mark Dickinson
........
r58295 | facundo.batista | 2007-10-02 11:21:18 -0700 (Tue, 02 Oct 2007) | 4 lines
Added a class to store the digits of log(10), so that they can be made
available when necessary without recomputing. Thanks Mark Dickinson
........
r58299 | mark.summerfield | 2007-10-03 01:53:21 -0700 (Wed, 03 Oct 2007) | 4 lines
Added note in footnote about string comparisons about
unicodedata.normalize().
........
r58304 | raymond.hettinger | 2007-10-03 14:18:11 -0700 (Wed, 03 Oct 2007) | 1 line
enumerate() is no longer bounded to using sequences shorter than LONG_MAX. The possibility of overflow was sending some newsgroup posters into a tizzy.
........
r58305 | raymond.hettinger | 2007-10-03 17:20:27 -0700 (Wed, 03 Oct 2007) | 1 line
itertools.count() no longer limited to sys.maxint.
........
r58306 | kurt.kaiser | 2007-10-03 18:49:54 -0700 (Wed, 03 Oct 2007) | 3 lines
Assume that the user knows when he wants to end the line; don't insert
something he didn't select or complete.
........
r58307 | kurt.kaiser | 2007-10-03 19:07:50 -0700 (Wed, 03 Oct 2007) | 2 lines
Remove unused theme that was causing a fault in p3k.
........
r58308 | kurt.kaiser | 2007-10-03 19:09:17 -0700 (Wed, 03 Oct 2007) | 2 lines
Clean up EditorWindow close.
........
r58309 | kurt.kaiser | 2007-10-03 19:53:07 -0700 (Wed, 03 Oct 2007) | 7 lines
textView cleanup. Patch 1718043 Tal Einat.
M idlelib/EditorWindow.py
M idlelib/aboutDialog.py
M idlelib/textView.py
M idlelib/NEWS.txt
........
r58310 | kurt.kaiser | 2007-10-03 20:11:12 -0700 (Wed, 03 Oct 2007) | 3 lines
configDialog cleanup. Patch 1730217 Tal Einat.
........
r58311 | neal.norwitz | 2007-10-03 23:00:48 -0700 (Wed, 03 Oct 2007) | 4 lines
Coverity #151: Remove deadcode.
All this code already exists above starting at line 653.
........
r58325 | fred.drake | 2007-10-04 19:46:12 -0700 (Thu, 04 Oct 2007) | 1 line
wrap lines to <80 characters before fixing errors
........
r58326 | raymond.hettinger | 2007-10-04 19:47:07 -0700 (Thu, 04 Oct 2007) | 6 lines
Add __asdict__() to NamedTuple and refine the docs.
Add maxlen support to deque() and fixup docs.
Partially fix __reduce__(). The None as a third arg was no longer supported.
Still needs work on __reduce__() to handle recursive inputs.
........
r58327 | fred.drake | 2007-10-04 19:48:32 -0700 (Thu, 04 Oct 2007) | 3 lines
move descriptions of ac_(in|out)_buffer_size to the right place
http://bugs.python.org/issue1053
........
r58329 | neal.norwitz | 2007-10-04 20:39:17 -0700 (Thu, 04 Oct 2007) | 3 lines
dict could be NULL, so we need to XDECREF.
Fix a compiler warning about passing a PyTypeObject* instead of PyObject*.
........
r58330 | neal.norwitz | 2007-10-04 20:41:19 -0700 (Thu, 04 Oct 2007) | 2 lines
Fix Coverity #158: Check the correct variable.
........
r58332 | neal.norwitz | 2007-10-04 22:01:38 -0700 (Thu, 04 Oct 2007) | 7 lines
Fix Coverity #159.
This code was broken if save() returned a negative number since i contained
a boolean value and then we compared i < 0 which should never be true.
Will backport (assuming it's necessary)
........
r58334 | neal.norwitz | 2007-10-04 22:29:17 -0700 (Thu, 04 Oct 2007) | 1 line
Add a note about fixing some more warnings found by Coverity.
........
r58338 | raymond.hettinger | 2007-10-05 12:07:31 -0700 (Fri, 05 Oct 2007) | 1 line
Restore BEGIN/END THREADS macros which were squashed in the previous checkin
........
r58343 | gregory.p.smith | 2007-10-06 00:48:10 -0700 (Sat, 06 Oct 2007) | 3 lines
Stab in the dark attempt to fix the test_bsddb3 failure on sparc and S-390
ubuntu buildbots.
........
r58344 | gregory.p.smith | 2007-10-06 00:51:59 -0700 (Sat, 06 Oct 2007) | 2 lines
Allows BerkeleyDB 4.6.x >= 4.6.21 for the bsddb module.
........
r58348 | gregory.p.smith | 2007-10-06 08:47:37 -0700 (Sat, 06 Oct 2007) | 3 lines
Use the host the author likely meant in the first place. pop.gmail.com is
reliable. gmail.org is someones personal domain.
........
r58351 | neal.norwitz | 2007-10-06 12:16:28 -0700 (Sat, 06 Oct 2007) | 3 lines
Ensure that this test will pass even if another test left an unwritable TESTFN.
Also use the safe unlink in test_support instead of rolling our own here.
........
r58368 | georg.brandl | 2007-10-08 00:50:24 -0700 (Mon, 08 Oct 2007) | 3 lines
#1123: fix the docs for the str.split(None, sep) case.
Also expand a few other methods' docs, which had more info in the deprecated string module docs.
........
r58369 | georg.brandl | 2007-10-08 01:06:05 -0700 (Mon, 08 Oct 2007) | 2 lines
Update docstring of sched, also remove an unused assignment.
........
r58370 | raymond.hettinger | 2007-10-08 02:14:28 -0700 (Mon, 08 Oct 2007) | 5 lines
Add comments to NamedTuple code.
Let the field spec be either a string or a non-string sequence (suggested by Martin Blais with use cases).
Improve the error message in the case of a SyntaxError (caused by a duplicate field name).
........
r58371 | raymond.hettinger | 2007-10-08 02:56:29 -0700 (Mon, 08 Oct 2007) | 1 line
Missed a line in the docs
........
r58372 | raymond.hettinger | 2007-10-08 03:11:51 -0700 (Mon, 08 Oct 2007) | 1 line
Better variable names
........
r58376 | georg.brandl | 2007-10-08 07:12:47 -0700 (Mon, 08 Oct 2007) | 3 lines
#1199: docs for tp_as_{number,sequence,mapping}, by Amaury Forgeot d'Arc.
No need to merge this to py3k!
........
r58380 | raymond.hettinger | 2007-10-08 14:26:58 -0700 (Mon, 08 Oct 2007) | 1 line
Eliminate camelcase function name
........
r58381 | andrew.kuchling | 2007-10-08 16:23:03 -0700 (Mon, 08 Oct 2007) | 1 line
Eliminate camelcase function name
........
r58382 | raymond.hettinger | 2007-10-08 18:36:23 -0700 (Mon, 08 Oct 2007) | 1 line
Make the error messages more specific
........
r58384 | gregory.p.smith | 2007-10-08 23:02:21 -0700 (Mon, 08 Oct 2007) | 10 lines
Splits Modules/_bsddb.c up into bsddb.h and _bsddb.c and adds a C API
object available as bsddb.db.api. This is based on the patch submitted
by Duncan Grisby here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1551895&group_id=13900&atid=313900
See this thread for additional info:
http://sourceforge.net/mailarchive/forum.php?thread_name=E1GAVDK-0002rk-Iw%40apasphere.com&forum_name=pybsddb-users
It also cleans up the code a little by removing some ifdef/endifs for
python prior to 2.1 and for unsupported Berkeley DB <= 3.2.
........
r58385 | gregory.p.smith | 2007-10-08 23:50:43 -0700 (Mon, 08 Oct 2007) | 5 lines
Fix a double free when positioning a database cursor to a non-existant
string key (and probably a few other situations with string keys).
This was reported with a patch as pybsddb sourceforge bug 1708868 by
jjjhhhlll at gmail.
........
r58386 | gregory.p.smith | 2007-10-09 00:19:11 -0700 (Tue, 09 Oct 2007) | 3 lines
Use the highest cPickle protocol in bsddb.dbshelve. This comes from
sourceforge pybsddb patch 1551443 by w_barnes.
........
r58394 | gregory.p.smith | 2007-10-09 11:26:02 -0700 (Tue, 09 Oct 2007) | 2 lines
remove another sleepycat reference
........
r58396 | kurt.kaiser | 2007-10-09 12:31:30 -0700 (Tue, 09 Oct 2007) | 3 lines
Allow interrupt only when executing user code in subprocess
Patch 1225 Tal Einat modified from IDLE-Spoon.
........
r58399 | brett.cannon | 2007-10-09 17:07:50 -0700 (Tue, 09 Oct 2007) | 5 lines
Remove file-level typedefs that were inconsistently used throughout the file.
Just move over to the public API names.
Closes issue1238.
........
r58401 | raymond.hettinger | 2007-10-09 17:26:46 -0700 (Tue, 09 Oct 2007) | 1 line
Accept Jim Jewett's api suggestion to use None instead of -1 to indicate unbounded deques.
........
r58403 | kurt.kaiser | 2007-10-09 17:55:40 -0700 (Tue, 09 Oct 2007) | 2 lines
Allow cursor color change w/o restart. Patch 1725576 Tal Einat.
........
r58404 | kurt.kaiser | 2007-10-09 18:06:47 -0700 (Tue, 09 Oct 2007) | 2 lines
show paste if > 80 columns. Patch 1659326 Tal Einat.
........
r58415 | thomas.heller | 2007-10-11 12:51:32 -0700 (Thu, 11 Oct 2007) | 5 lines
On OS X, use os.uname() instead of gestalt.sysv(...) to get the
operating system version. This allows to use ctypes when Python
was configured with --disable-toolbox-glue.
........
r58419 | neal.norwitz | 2007-10-11 20:01:01 -0700 (Thu, 11 Oct 2007) | 1 line
Get rid of warning about not being able to create an existing directory.
........
r58420 | neal.norwitz | 2007-10-11 20:01:30 -0700 (Thu, 11 Oct 2007) | 1 line
Get rid of warnings on a bunch of platforms by using a proper prototype.
........
r58421 | neal.norwitz | 2007-10-11 20:01:54 -0700 (Thu, 11 Oct 2007) | 4 lines
Get rid of compiler warning about retval being used (returned) without
being initialized. (gcc warning and Coverity 202)
........
r58422 | neal.norwitz | 2007-10-11 20:03:23 -0700 (Thu, 11 Oct 2007) | 1 line
Fix Coverity 168: Close the file before returning (exiting).
........
r58423 | neal.norwitz | 2007-10-11 20:04:18 -0700 (Thu, 11 Oct 2007) | 4 lines
Fix Coverity 180: Don't overallocate. We don't need structs, but pointers.
Also fix a memory leak.
........
r58424 | neal.norwitz | 2007-10-11 20:05:19 -0700 (Thu, 11 Oct 2007) | 5 lines
Fix Coverity 185-186: If the passed in FILE is NULL, uninitialized memory
would be accessed.
Will backport.
........
r58425 | neal.norwitz | 2007-10-11 20:52:34 -0700 (Thu, 11 Oct 2007) | 1 line
Get this module to compile with bsddb versions prior to 4.3
........
r58430 | martin.v.loewis | 2007-10-12 01:56:52 -0700 (Fri, 12 Oct 2007) | 3 lines
Bug #1216: Restore support for Visual Studio 2002.
Will backport to 2.5.
........
r58433 | raymond.hettinger | 2007-10-12 10:53:11 -0700 (Fri, 12 Oct 2007) | 1 line
Fix test of count.__repr__() to ignore the 'L' if the count is a long
........
r58434 | gregory.p.smith | 2007-10-12 11:44:06 -0700 (Fri, 12 Oct 2007) | 4 lines
Fixes http://bugs.python.org/issue1233 - bsddb.dbshelve.DBShelf.append
was useless due to inverted logic. Also adds a test case for RECNO dbs
to test_dbshelve.
........
r58445 | georg.brandl | 2007-10-13 06:20:03 -0700 (Sat, 13 Oct 2007) | 2 lines
Fix email example.
........
r58450 | gregory.p.smith | 2007-10-13 16:02:05 -0700 (Sat, 13 Oct 2007) | 2 lines
Fix an uncollectable reference leak in bsddb.db.DBShelf.append
........
r58453 | neal.norwitz | 2007-10-13 17:18:40 -0700 (Sat, 13 Oct 2007) | 8 lines
Let the O/S supply a port if none of the default ports can be used.
This should make the tests more robust at the expense of allowing
tests to be sloppier by not requiring them to cleanup after themselves.
(It will legitamitely help when running two test suites simultaneously
or if another process is already using one of the predefined ports.)
Also simplifies (slightLy) the exception handling elsewhere.
........
r58459 | neal.norwitz | 2007-10-14 11:30:21 -0700 (Sun, 14 Oct 2007) | 2 lines
Don't raise a string exception, they don't work anymore.
........
r58460 | neal.norwitz | 2007-10-14 11:40:37 -0700 (Sun, 14 Oct 2007) | 1 line
Use unittest for assertions
........
r58468 | armin.rigo | 2007-10-15 00:48:35 -0700 (Mon, 15 Oct 2007) | 2 lines
test_bigbits was not testing what it seemed to.
........
r58471 | guido.van.rossum | 2007-10-15 08:54:11 -0700 (Mon, 15 Oct 2007) | 3 lines
Change a PyErr_Print() into a PyErr_Clear(),
per discussion in issue 1031213.
........
r58500 | raymond.hettinger | 2007-10-16 12:18:30 -0700 (Tue, 16 Oct 2007) | 1 line
Improve error messages
........
r58506 | raymond.hettinger | 2007-10-16 14:28:32 -0700 (Tue, 16 Oct 2007) | 1 line
More docs, error messages, and tests
........
r58507 | andrew.kuchling | 2007-10-16 15:58:03 -0700 (Tue, 16 Oct 2007) | 1 line
Add items
........
r58508 | brett.cannon | 2007-10-16 16:24:06 -0700 (Tue, 16 Oct 2007) | 3 lines
Remove ``:const:`` notation on None in parameter list. Since the markup is not
rendered for parameters it just showed up as ``:const:`None` `` in the output.
........
r58509 | brett.cannon | 2007-10-16 16:26:45 -0700 (Tue, 16 Oct 2007) | 3 lines
Re-order some functions whose parameters differ between PyObject and const char
* so that they are next to each other.
........
r58522 | armin.rigo | 2007-10-17 11:46:37 -0700 (Wed, 17 Oct 2007) | 5 lines
Fix the overflow checking of list_repeat.
Introduce overflow checking into list_inplace_repeat.
Backport candidate, possibly.
........
r58530 | facundo.batista | 2007-10-17 20:16:03 -0700 (Wed, 17 Oct 2007) | 7 lines
Issue #1580738. When HTTPConnection reads the whole stream with read(),
it closes itself. When the stream is read in several calls to read(n),
it should behave in the same way if HTTPConnection knows where the end
of the stream is (through self.length). Added a test case for this
behaviour.
........
r58531 | facundo.batista | 2007-10-17 20:44:48 -0700 (Wed, 17 Oct 2007) | 3 lines
Issue 1289, just a typo.
........
r58532 | gregory.p.smith | 2007-10-18 00:56:54 -0700 (Thu, 18 Oct 2007) | 4 lines
cleanup test_dbtables to use mkdtemp. cleanup dbtables to pass txn as a
keyword argument whenever possible to avoid bugs and confusion. (dbtables.py
line 447 self.db.get using txn as a non-keyword was an actual bug due to this)
........
r58533 | gregory.p.smith | 2007-10-18 01:34:20 -0700 (Thu, 18 Oct 2007) | 4 lines
Fix a weird bug in dbtables: if it chose a random rowid string that contained
NULL bytes it would cause the database all sorts of problems in the future
leading to very strange random failures and corrupt dbtables.bsdTableDb dbs.
........
r58534 | gregory.p.smith | 2007-10-18 09:32:02 -0700 (Thu, 18 Oct 2007) | 3 lines
A cleaner fix than the one committed last night. Generate random rowids that
do not contain null bytes.
........
r58537 | gregory.p.smith | 2007-10-18 10:17:57 -0700 (Thu, 18 Oct 2007) | 2 lines
mention bsddb fixes.
........
r58538 | raymond.hettinger | 2007-10-18 14:13:06 -0700 (Thu, 18 Oct 2007) | 1 line
Remove useless warning
........
r58539 | gregory.p.smith | 2007-10-19 00:31:20 -0700 (Fri, 19 Oct 2007) | 2 lines
squelch the warning that this test is supposed to trigger.
........
r58542 | georg.brandl | 2007-10-19 05:32:39 -0700 (Fri, 19 Oct 2007) | 2 lines
Clarify wording for apply().
........
r58544 | mark.summerfield | 2007-10-19 05:48:17 -0700 (Fri, 19 Oct 2007) | 3 lines
Added a cross-ref to each other.
........
r58545 | georg.brandl | 2007-10-19 10:38:49 -0700 (Fri, 19 Oct 2007) | 2 lines
#1284: "S" means "seen", not unread.
........
r58548 | thomas.heller | 2007-10-19 11:11:41 -0700 (Fri, 19 Oct 2007) | 4 lines
Fix ctypes on 32-bit systems when Python is configured --with-system-ffi.
See also https://bugs.launchpad.net/bugs/72505.
Ported from release25-maint branch.
........
r58550 | facundo.batista | 2007-10-19 12:25:57 -0700 (Fri, 19 Oct 2007) | 8 lines
The constructor from tuple was way too permissive: it allowed bad
coefficient numbers, floats in the sign, and other details that
generated directly the wrong number in the best case, or triggered
misfunctionality in the alorithms.
Test cases added for these issues. Thanks Mark Dickinson.
........
r58559 | georg.brandl | 2007-10-20 06:22:53 -0700 (Sat, 20 Oct 2007) | 2 lines
Fix code being interpreted as a target.
........
r58561 | georg.brandl | 2007-10-20 06:36:24 -0700 (Sat, 20 Oct 2007) | 2 lines
Document new "cmdoption" directive.
........
r58562 | georg.brandl | 2007-10-20 08:21:22 -0700 (Sat, 20 Oct 2007) | 2 lines
Make a path more Unix-standardy.
........
r58564 | georg.brandl | 2007-10-20 10:51:39 -0700 (Sat, 20 Oct 2007) | 2 lines
Document new directive "envvar".
........
r58567 | georg.brandl | 2007-10-20 11:08:14 -0700 (Sat, 20 Oct 2007) | 6 lines
* Add new toplevel chapter, "Using Python." (how to install,
configure and setup python on different platforms -- at least
in theory.)
* Move the Python on Mac docs in that chapter.
* Add a new chapter about the command line invocation, by stargaming.
........
r58568 | georg.brandl | 2007-10-20 11:33:20 -0700 (Sat, 20 Oct 2007) | 2 lines
Change title, for now.
........
r58569 | georg.brandl | 2007-10-20 11:39:25 -0700 (Sat, 20 Oct 2007) | 2 lines
Add entry to ACKS.
........
r58570 | georg.brandl | 2007-10-20 12:05:45 -0700 (Sat, 20 Oct 2007) | 2 lines
Clarify -E docs.
........
r58571 | georg.brandl | 2007-10-20 12:08:36 -0700 (Sat, 20 Oct 2007) | 2 lines
Even more clarification.
........
r58572 | andrew.kuchling | 2007-10-20 12:25:37 -0700 (Sat, 20 Oct 2007) | 1 line
Fix protocol name
........
r58573 | andrew.kuchling | 2007-10-20 12:35:18 -0700 (Sat, 20 Oct 2007) | 1 line
Various items
........
r58574 | andrew.kuchling | 2007-10-20 12:39:35 -0700 (Sat, 20 Oct 2007) | 1 line
Use correct header line
........
r58576 | armin.rigo | 2007-10-21 02:14:15 -0700 (Sun, 21 Oct 2007) | 3 lines
Add a crasher for the long-standing issue with closing a file
while another thread uses it.
........
r58577 | georg.brandl | 2007-10-21 03:01:56 -0700 (Sun, 21 Oct 2007) | 2 lines
Remove duplicate crasher.
........
r58578 | georg.brandl | 2007-10-21 03:24:20 -0700 (Sun, 21 Oct 2007) | 2 lines
Unify "byte code" to "bytecode". Also sprinkle :term: markup for it.
........
r58579 | georg.brandl | 2007-10-21 03:32:54 -0700 (Sun, 21 Oct 2007) | 2 lines
Add markup to new function descriptions.
........
r58580 | georg.brandl | 2007-10-21 03:45:46 -0700 (Sun, 21 Oct 2007) | 2 lines
Add :term:s for descriptors.
........
r58581 | georg.brandl | 2007-10-21 03:46:24 -0700 (Sun, 21 Oct 2007) | 2 lines
Unify "file-descriptor" to "file descriptor".
........
r58582 | georg.brandl | 2007-10-21 03:52:38 -0700 (Sun, 21 Oct 2007) | 2 lines
Add :term: for generators.
........
r58583 | georg.brandl | 2007-10-21 05:10:28 -0700 (Sun, 21 Oct 2007) | 2 lines
Add :term:s for iterator.
........
r58584 | georg.brandl | 2007-10-21 05:15:05 -0700 (Sun, 21 Oct 2007) | 2 lines
Add :term:s for "new-style class".
........
r58588 | neal.norwitz | 2007-10-21 21:47:54 -0700 (Sun, 21 Oct 2007) | 1 line
Add Chris Monson so he can edit PEPs.
........
r58594 | guido.van.rossum | 2007-10-22 09:27:19 -0700 (Mon, 22 Oct 2007) | 4 lines
Issue #1307, patch by Derek Shockey.
When "MAIL" is received without args, an exception happens instead of
sending a 501 syntax error response.
........
r58598 | travis.oliphant | 2007-10-22 19:40:56 -0700 (Mon, 22 Oct 2007) | 1 line
Add phuang patch from Issue 708374 which adds offset parameter to mmap module.
........
r58601 | neal.norwitz | 2007-10-22 22:44:27 -0700 (Mon, 22 Oct 2007) | 2 lines
Bug #1313, fix typo (wrong variable name) in example.
........
r58609 | georg.brandl | 2007-10-23 11:21:35 -0700 (Tue, 23 Oct 2007) | 2 lines
Update Pygments version from externals.
........
r58618 | guido.van.rossum | 2007-10-23 12:25:41 -0700 (Tue, 23 Oct 2007) | 3 lines
Issue 1307 by Derek Shockey, fox the same bug for RCPT.
Neal: please backport!
........
r58620 | raymond.hettinger | 2007-10-23 13:37:41 -0700 (Tue, 23 Oct 2007) | 1 line
Shorter name for namedtuple()
........
r58621 | andrew.kuchling | 2007-10-23 13:55:47 -0700 (Tue, 23 Oct 2007) | 1 line
Update name
........
r58622 | raymond.hettinger | 2007-10-23 14:23:07 -0700 (Tue, 23 Oct 2007) | 1 line
Fixup news entry
........
r58623 | raymond.hettinger | 2007-10-23 18:28:33 -0700 (Tue, 23 Oct 2007) | 1 line
Optimize sum() for integer and float inputs.
........
r58624 | raymond.hettinger | 2007-10-23 19:05:51 -0700 (Tue, 23 Oct 2007) | 1 line
Fixup error return and add support for intermixed ints and floats/
........
r58628 | vinay.sajip | 2007-10-24 03:47:06 -0700 (Wed, 24 Oct 2007) | 1 line
Bug #1321: Fixed logic error in TimedRotatingFileHandler.__init__()
........
r58641 | facundo.batista | 2007-10-24 12:11:08 -0700 (Wed, 24 Oct 2007) | 4 lines
Issue 1290. CharacterData.__repr__ was constructing a string
in response that keeped having a non-ascii character.
........
r58643 | thomas.heller | 2007-10-24 12:50:45 -0700 (Wed, 24 Oct 2007) | 1 line
Added unittest for calling a function with paramflags (backport from py3k branch).
........
r58645 | matthias.klose | 2007-10-24 13:00:44 -0700 (Wed, 24 Oct 2007) | 2 lines
- Build using system ffi library on arm*-linux*.
........
r58651 | georg.brandl | 2007-10-24 14:40:38 -0700 (Wed, 24 Oct 2007) | 2 lines
Bug #1287: make os.environ.pop() work as expected.
........
r58652 | raymond.hettinger | 2007-10-24 19:26:58 -0700 (Wed, 24 Oct 2007) | 1 line
Missing DECREFs
........
r58653 | matthias.klose | 2007-10-24 23:37:24 -0700 (Wed, 24 Oct 2007) | 2 lines
- Build using system ffi library on arm*-linux*, pass --with-system-ffi to CONFIG_ARGS
........
r58655 | thomas.heller | 2007-10-25 12:47:32 -0700 (Thu, 25 Oct 2007) | 2 lines
ffi_type_longdouble may be already #defined.
See issue 1324.
........
r58656 | kurt.kaiser | 2007-10-25 15:43:45 -0700 (Thu, 25 Oct 2007) | 3 lines
Correct an ancient bug in an unused path by removing that path: register() is
now idempotent.
........
r58660 | kurt.kaiser | 2007-10-25 17:10:09 -0700 (Thu, 25 Oct 2007) | 4 lines
1. Add comments to provide top-level documentation.
2. Refactor to use more descriptive names.
3. Enhance tests in main().
........
r58675 | georg.brandl | 2007-10-26 11:30:41 -0700 (Fri, 26 Oct 2007) | 2 lines
Fix new pop() method on os.environ on ignorecase-platforms.
........
r58696 | neal.norwitz | 2007-10-27 15:32:21 -0700 (Sat, 27 Oct 2007) | 1 line
Update URL for Pygments. 0.8.1 is no longer available
........
r58697 | hyeshik.chang | 2007-10-28 04:19:02 -0700 (Sun, 28 Oct 2007) | 3 lines
- Add support for FreeBSD 8 which is recently forked from FreeBSD 7.
- Regenerate IN module for most recent maintenance tree of FreeBSD 6 and 7.
........
r58698 | hyeshik.chang | 2007-10-28 05:38:09 -0700 (Sun, 28 Oct 2007) | 2 lines
Enable platform-specific tweaks for FreeBSD 8 (exactly same to FreeBSD 7's yet)
........
r58700 | kurt.kaiser | 2007-10-28 12:03:59 -0700 (Sun, 28 Oct 2007) | 2 lines
Add confirmation dialog before printing. Patch 1717170 Tal Einat.
........
r58706 | guido.van.rossum | 2007-10-29 13:52:45 -0700 (Mon, 29 Oct 2007) | 3 lines
Patch 1353 by Jacob Winther.
Add mp4 mapping to mimetypes.py.
........
r58709 | guido.van.rossum | 2007-10-29 15:15:05 -0700 (Mon, 29 Oct 2007) | 6 lines
Backport fixes for the code that decodes octal escapes (and for PyString
also hex escapes) -- this was reaching beyond the end of the input string
buffer, even though it is not supposed to be \0-terminated.
This has no visible effect but is clearly the correct thing to do.
(In 3.0 it had a visible effect after removing ob_sstate from PyString.)
........
r58710 | kurt.kaiser | 2007-10-29 19:38:54 -0700 (Mon, 29 Oct 2007) | 7 lines
check in Tal Einat's update to tabpage.py
Patch 1612746
M configDialog.py
M NEWS.txt
AM tabbedpages.py
........
r58715 | georg.brandl | 2007-10-30 10:51:18 -0700 (Tue, 30 Oct 2007) | 2 lines
Use correct markup.
........
r58716 | georg.brandl | 2007-10-30 10:57:12 -0700 (Tue, 30 Oct 2007) | 2 lines
Make example about hiding None return values at the prompt clearer.
........
r58728 | neal.norwitz | 2007-10-30 23:33:20 -0700 (Tue, 30 Oct 2007) | 1 line
Fix some compiler warnings for signed comparisons on Unix and Windows.
........
r58731 | martin.v.loewis | 2007-10-31 10:19:33 -0700 (Wed, 31 Oct 2007) | 2 lines
Adding Christian Heimes.
........
r58737 | raymond.hettinger | 2007-10-31 14:57:58 -0700 (Wed, 31 Oct 2007) | 1 line
Clarify the reasons why pickle is almost always better than marshal
........
r58739 | raymond.hettinger | 2007-10-31 15:15:49 -0700 (Wed, 31 Oct 2007) | 1 line
Sets are marshalable.
........
2007-11-01 17:32:30 -03:00
|
|
|
type object to create :term:`descriptor`\s which are placed in the dictionary of the
|
2007-08-15 11:28:22 -03:00
|
|
|
type object. Each descriptor controls access to one attribute of the instance
|
|
|
|
object. Each of the tables is optional; if all three are *NULL*, instances of
|
|
|
|
the type will only have attributes that are inherited from their base type, and
|
2013-08-01 16:12:45 -03:00
|
|
|
should leave the :c:member:`~PyTypeObject.tp_getattro` and :c:member:`~PyTypeObject.tp_setattro` fields *NULL* as
|
2007-08-15 11:28:22 -03:00
|
|
|
well, allowing the base type to handle attributes.
|
|
|
|
|
|
|
|
The tables are declared as three fields of the type object::
|
|
|
|
|
|
|
|
struct PyMethodDef *tp_methods;
|
|
|
|
struct PyMemberDef *tp_members;
|
|
|
|
struct PyGetSetDef *tp_getset;
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
If :c:member:`~PyTypeObject.tp_methods` is not *NULL*, it must refer to an array of
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:type:`PyMethodDef` structures. Each entry in the table is an instance of this
|
2007-08-15 11:28:22 -03:00
|
|
|
structure::
|
|
|
|
|
|
|
|
typedef struct PyMethodDef {
|
2016-11-21 05:37:18 -04:00
|
|
|
const char *ml_name; /* method name */
|
2007-08-15 11:28:22 -03:00
|
|
|
PyCFunction ml_meth; /* implementation function */
|
2009-01-03 17:26:05 -04:00
|
|
|
int ml_flags; /* flags */
|
2016-11-21 05:37:18 -04:00
|
|
|
const char *ml_doc; /* docstring */
|
2007-08-15 11:28:22 -03:00
|
|
|
} PyMethodDef;
|
|
|
|
|
|
|
|
One entry should be defined for each method provided by the type; no entries are
|
|
|
|
needed for methods inherited from a base type. One additional entry is needed
|
|
|
|
at the end; it is a sentinel that marks the end of the array. The
|
|
|
|
:attr:`ml_name` field of the sentinel must be *NULL*.
|
|
|
|
|
|
|
|
The second table is used to define attributes which map directly to data stored
|
|
|
|
in the instance. A variety of primitive C types are supported, and access may
|
|
|
|
be read-only or read-write. The structures in the table are defined as::
|
|
|
|
|
|
|
|
typedef struct PyMemberDef {
|
|
|
|
char *name;
|
|
|
|
int type;
|
|
|
|
int offset;
|
|
|
|
int flags;
|
|
|
|
char *doc;
|
|
|
|
} PyMemberDef;
|
|
|
|
|
#1370: Finish the merge r58749, log below, by resolving all conflicts in Doc/.
Merged revisions 58221-58741 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk
........
r58221 | georg.brandl | 2007-09-20 10:57:59 -0700 (Thu, 20 Sep 2007) | 2 lines
Patch #1181: add os.environ.clear() method.
........
r58225 | sean.reifschneider | 2007-09-20 23:33:28 -0700 (Thu, 20 Sep 2007) | 3 lines
Issue1704287: "make install" fails unless you do "make" first. Make
oldsharedmods and sharedmods in "libinstall".
........
r58232 | guido.van.rossum | 2007-09-22 13:18:03 -0700 (Sat, 22 Sep 2007) | 4 lines
Patch # 188 by Philip Jenvey.
Make tell() mark CRLF as a newline.
With unit test.
........
r58242 | georg.brandl | 2007-09-24 10:55:47 -0700 (Mon, 24 Sep 2007) | 2 lines
Fix typo and double word.
........
r58245 | georg.brandl | 2007-09-24 10:59:28 -0700 (Mon, 24 Sep 2007) | 2 lines
#1196: document default radix for int().
........
r58247 | georg.brandl | 2007-09-24 11:08:24 -0700 (Mon, 24 Sep 2007) | 2 lines
#1177: accept 2xx responses for https too, not only http.
........
r58249 | andrew.kuchling | 2007-09-24 16:45:51 -0700 (Mon, 24 Sep 2007) | 1 line
Remove stray odd character; grammar fix
........
r58250 | andrew.kuchling | 2007-09-24 16:46:28 -0700 (Mon, 24 Sep 2007) | 1 line
Typo fix
........
r58251 | andrew.kuchling | 2007-09-24 17:09:42 -0700 (Mon, 24 Sep 2007) | 1 line
Add various items
........
r58268 | vinay.sajip | 2007-09-26 22:34:45 -0700 (Wed, 26 Sep 2007) | 1 line
Change to flush and close logic to fix #1760556.
........
r58269 | vinay.sajip | 2007-09-26 22:38:51 -0700 (Wed, 26 Sep 2007) | 1 line
Change to basicConfig() to fix #1021.
........
r58270 | georg.brandl | 2007-09-26 23:26:58 -0700 (Wed, 26 Sep 2007) | 2 lines
#1208: document match object's boolean value.
........
r58271 | vinay.sajip | 2007-09-26 23:56:13 -0700 (Wed, 26 Sep 2007) | 1 line
Minor date change.
........
r58272 | vinay.sajip | 2007-09-27 00:35:10 -0700 (Thu, 27 Sep 2007) | 1 line
Change to LogRecord.__init__() to fix #1206. Note that archaic use of type(x) == types.DictType is because of keeping 1.5.2 compatibility. While this is much less relevant these days, there probably needs to be a separate commit for removing all archaic constructs at the same time.
........
r58288 | brett.cannon | 2007-09-30 12:45:10 -0700 (Sun, 30 Sep 2007) | 9 lines
tuple.__repr__ did not consider a reference loop as it is not possible from
Python code; but it is possible from C. object.__str__ had the issue of not
expecting a type to doing something within it's tp_str implementation that
could trigger an infinite recursion, but it could in C code.. Both found
thanks to BaseException and how it handles its repr.
Closes issue #1686386. Thanks to Thomas Herve for taking an initial stab at
coming up with a solution.
........
r58289 | brett.cannon | 2007-09-30 13:37:19 -0700 (Sun, 30 Sep 2007) | 3 lines
Fix error introduced by r58288; if a tuple is length 0 return its repr and
don't worry about any self-referring tuples.
........
r58294 | facundo.batista | 2007-10-02 10:01:24 -0700 (Tue, 02 Oct 2007) | 11 lines
Made the various is_* operations return booleans. This was discussed
with Cawlishaw by mail, and he basically confirmed that to these is_*
operations, there's no need to return Decimal(0) and Decimal(1) if
the language supports the False and True booleans.
Also added a few tests for the these functions in extra.decTest, since
they are mostly untested (apart from the doctests).
Thanks Mark Dickinson
........
r58295 | facundo.batista | 2007-10-02 11:21:18 -0700 (Tue, 02 Oct 2007) | 4 lines
Added a class to store the digits of log(10), so that they can be made
available when necessary without recomputing. Thanks Mark Dickinson
........
r58299 | mark.summerfield | 2007-10-03 01:53:21 -0700 (Wed, 03 Oct 2007) | 4 lines
Added note in footnote about string comparisons about
unicodedata.normalize().
........
r58304 | raymond.hettinger | 2007-10-03 14:18:11 -0700 (Wed, 03 Oct 2007) | 1 line
enumerate() is no longer bounded to using sequences shorter than LONG_MAX. The possibility of overflow was sending some newsgroup posters into a tizzy.
........
r58305 | raymond.hettinger | 2007-10-03 17:20:27 -0700 (Wed, 03 Oct 2007) | 1 line
itertools.count() no longer limited to sys.maxint.
........
r58306 | kurt.kaiser | 2007-10-03 18:49:54 -0700 (Wed, 03 Oct 2007) | 3 lines
Assume that the user knows when he wants to end the line; don't insert
something he didn't select or complete.
........
r58307 | kurt.kaiser | 2007-10-03 19:07:50 -0700 (Wed, 03 Oct 2007) | 2 lines
Remove unused theme that was causing a fault in p3k.
........
r58308 | kurt.kaiser | 2007-10-03 19:09:17 -0700 (Wed, 03 Oct 2007) | 2 lines
Clean up EditorWindow close.
........
r58309 | kurt.kaiser | 2007-10-03 19:53:07 -0700 (Wed, 03 Oct 2007) | 7 lines
textView cleanup. Patch 1718043 Tal Einat.
M idlelib/EditorWindow.py
M idlelib/aboutDialog.py
M idlelib/textView.py
M idlelib/NEWS.txt
........
r58310 | kurt.kaiser | 2007-10-03 20:11:12 -0700 (Wed, 03 Oct 2007) | 3 lines
configDialog cleanup. Patch 1730217 Tal Einat.
........
r58311 | neal.norwitz | 2007-10-03 23:00:48 -0700 (Wed, 03 Oct 2007) | 4 lines
Coverity #151: Remove deadcode.
All this code already exists above starting at line 653.
........
r58325 | fred.drake | 2007-10-04 19:46:12 -0700 (Thu, 04 Oct 2007) | 1 line
wrap lines to <80 characters before fixing errors
........
r58326 | raymond.hettinger | 2007-10-04 19:47:07 -0700 (Thu, 04 Oct 2007) | 6 lines
Add __asdict__() to NamedTuple and refine the docs.
Add maxlen support to deque() and fixup docs.
Partially fix __reduce__(). The None as a third arg was no longer supported.
Still needs work on __reduce__() to handle recursive inputs.
........
r58327 | fred.drake | 2007-10-04 19:48:32 -0700 (Thu, 04 Oct 2007) | 3 lines
move descriptions of ac_(in|out)_buffer_size to the right place
http://bugs.python.org/issue1053
........
r58329 | neal.norwitz | 2007-10-04 20:39:17 -0700 (Thu, 04 Oct 2007) | 3 lines
dict could be NULL, so we need to XDECREF.
Fix a compiler warning about passing a PyTypeObject* instead of PyObject*.
........
r58330 | neal.norwitz | 2007-10-04 20:41:19 -0700 (Thu, 04 Oct 2007) | 2 lines
Fix Coverity #158: Check the correct variable.
........
r58332 | neal.norwitz | 2007-10-04 22:01:38 -0700 (Thu, 04 Oct 2007) | 7 lines
Fix Coverity #159.
This code was broken if save() returned a negative number since i contained
a boolean value and then we compared i < 0 which should never be true.
Will backport (assuming it's necessary)
........
r58334 | neal.norwitz | 2007-10-04 22:29:17 -0700 (Thu, 04 Oct 2007) | 1 line
Add a note about fixing some more warnings found by Coverity.
........
r58338 | raymond.hettinger | 2007-10-05 12:07:31 -0700 (Fri, 05 Oct 2007) | 1 line
Restore BEGIN/END THREADS macros which were squashed in the previous checkin
........
r58343 | gregory.p.smith | 2007-10-06 00:48:10 -0700 (Sat, 06 Oct 2007) | 3 lines
Stab in the dark attempt to fix the test_bsddb3 failure on sparc and S-390
ubuntu buildbots.
........
r58344 | gregory.p.smith | 2007-10-06 00:51:59 -0700 (Sat, 06 Oct 2007) | 2 lines
Allows BerkeleyDB 4.6.x >= 4.6.21 for the bsddb module.
........
r58348 | gregory.p.smith | 2007-10-06 08:47:37 -0700 (Sat, 06 Oct 2007) | 3 lines
Use the host the author likely meant in the first place. pop.gmail.com is
reliable. gmail.org is someones personal domain.
........
r58351 | neal.norwitz | 2007-10-06 12:16:28 -0700 (Sat, 06 Oct 2007) | 3 lines
Ensure that this test will pass even if another test left an unwritable TESTFN.
Also use the safe unlink in test_support instead of rolling our own here.
........
r58368 | georg.brandl | 2007-10-08 00:50:24 -0700 (Mon, 08 Oct 2007) | 3 lines
#1123: fix the docs for the str.split(None, sep) case.
Also expand a few other methods' docs, which had more info in the deprecated string module docs.
........
r58369 | georg.brandl | 2007-10-08 01:06:05 -0700 (Mon, 08 Oct 2007) | 2 lines
Update docstring of sched, also remove an unused assignment.
........
r58370 | raymond.hettinger | 2007-10-08 02:14:28 -0700 (Mon, 08 Oct 2007) | 5 lines
Add comments to NamedTuple code.
Let the field spec be either a string or a non-string sequence (suggested by Martin Blais with use cases).
Improve the error message in the case of a SyntaxError (caused by a duplicate field name).
........
r58371 | raymond.hettinger | 2007-10-08 02:56:29 -0700 (Mon, 08 Oct 2007) | 1 line
Missed a line in the docs
........
r58372 | raymond.hettinger | 2007-10-08 03:11:51 -0700 (Mon, 08 Oct 2007) | 1 line
Better variable names
........
r58376 | georg.brandl | 2007-10-08 07:12:47 -0700 (Mon, 08 Oct 2007) | 3 lines
#1199: docs for tp_as_{number,sequence,mapping}, by Amaury Forgeot d'Arc.
No need to merge this to py3k!
........
r58380 | raymond.hettinger | 2007-10-08 14:26:58 -0700 (Mon, 08 Oct 2007) | 1 line
Eliminate camelcase function name
........
r58381 | andrew.kuchling | 2007-10-08 16:23:03 -0700 (Mon, 08 Oct 2007) | 1 line
Eliminate camelcase function name
........
r58382 | raymond.hettinger | 2007-10-08 18:36:23 -0700 (Mon, 08 Oct 2007) | 1 line
Make the error messages more specific
........
r58384 | gregory.p.smith | 2007-10-08 23:02:21 -0700 (Mon, 08 Oct 2007) | 10 lines
Splits Modules/_bsddb.c up into bsddb.h and _bsddb.c and adds a C API
object available as bsddb.db.api. This is based on the patch submitted
by Duncan Grisby here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1551895&group_id=13900&atid=313900
See this thread for additional info:
http://sourceforge.net/mailarchive/forum.php?thread_name=E1GAVDK-0002rk-Iw%40apasphere.com&forum_name=pybsddb-users
It also cleans up the code a little by removing some ifdef/endifs for
python prior to 2.1 and for unsupported Berkeley DB <= 3.2.
........
r58385 | gregory.p.smith | 2007-10-08 23:50:43 -0700 (Mon, 08 Oct 2007) | 5 lines
Fix a double free when positioning a database cursor to a non-existant
string key (and probably a few other situations with string keys).
This was reported with a patch as pybsddb sourceforge bug 1708868 by
jjjhhhlll at gmail.
........
r58386 | gregory.p.smith | 2007-10-09 00:19:11 -0700 (Tue, 09 Oct 2007) | 3 lines
Use the highest cPickle protocol in bsddb.dbshelve. This comes from
sourceforge pybsddb patch 1551443 by w_barnes.
........
r58394 | gregory.p.smith | 2007-10-09 11:26:02 -0700 (Tue, 09 Oct 2007) | 2 lines
remove another sleepycat reference
........
r58396 | kurt.kaiser | 2007-10-09 12:31:30 -0700 (Tue, 09 Oct 2007) | 3 lines
Allow interrupt only when executing user code in subprocess
Patch 1225 Tal Einat modified from IDLE-Spoon.
........
r58399 | brett.cannon | 2007-10-09 17:07:50 -0700 (Tue, 09 Oct 2007) | 5 lines
Remove file-level typedefs that were inconsistently used throughout the file.
Just move over to the public API names.
Closes issue1238.
........
r58401 | raymond.hettinger | 2007-10-09 17:26:46 -0700 (Tue, 09 Oct 2007) | 1 line
Accept Jim Jewett's api suggestion to use None instead of -1 to indicate unbounded deques.
........
r58403 | kurt.kaiser | 2007-10-09 17:55:40 -0700 (Tue, 09 Oct 2007) | 2 lines
Allow cursor color change w/o restart. Patch 1725576 Tal Einat.
........
r58404 | kurt.kaiser | 2007-10-09 18:06:47 -0700 (Tue, 09 Oct 2007) | 2 lines
show paste if > 80 columns. Patch 1659326 Tal Einat.
........
r58415 | thomas.heller | 2007-10-11 12:51:32 -0700 (Thu, 11 Oct 2007) | 5 lines
On OS X, use os.uname() instead of gestalt.sysv(...) to get the
operating system version. This allows to use ctypes when Python
was configured with --disable-toolbox-glue.
........
r58419 | neal.norwitz | 2007-10-11 20:01:01 -0700 (Thu, 11 Oct 2007) | 1 line
Get rid of warning about not being able to create an existing directory.
........
r58420 | neal.norwitz | 2007-10-11 20:01:30 -0700 (Thu, 11 Oct 2007) | 1 line
Get rid of warnings on a bunch of platforms by using a proper prototype.
........
r58421 | neal.norwitz | 2007-10-11 20:01:54 -0700 (Thu, 11 Oct 2007) | 4 lines
Get rid of compiler warning about retval being used (returned) without
being initialized. (gcc warning and Coverity 202)
........
r58422 | neal.norwitz | 2007-10-11 20:03:23 -0700 (Thu, 11 Oct 2007) | 1 line
Fix Coverity 168: Close the file before returning (exiting).
........
r58423 | neal.norwitz | 2007-10-11 20:04:18 -0700 (Thu, 11 Oct 2007) | 4 lines
Fix Coverity 180: Don't overallocate. We don't need structs, but pointers.
Also fix a memory leak.
........
r58424 | neal.norwitz | 2007-10-11 20:05:19 -0700 (Thu, 11 Oct 2007) | 5 lines
Fix Coverity 185-186: If the passed in FILE is NULL, uninitialized memory
would be accessed.
Will backport.
........
r58425 | neal.norwitz | 2007-10-11 20:52:34 -0700 (Thu, 11 Oct 2007) | 1 line
Get this module to compile with bsddb versions prior to 4.3
........
r58430 | martin.v.loewis | 2007-10-12 01:56:52 -0700 (Fri, 12 Oct 2007) | 3 lines
Bug #1216: Restore support for Visual Studio 2002.
Will backport to 2.5.
........
r58433 | raymond.hettinger | 2007-10-12 10:53:11 -0700 (Fri, 12 Oct 2007) | 1 line
Fix test of count.__repr__() to ignore the 'L' if the count is a long
........
r58434 | gregory.p.smith | 2007-10-12 11:44:06 -0700 (Fri, 12 Oct 2007) | 4 lines
Fixes http://bugs.python.org/issue1233 - bsddb.dbshelve.DBShelf.append
was useless due to inverted logic. Also adds a test case for RECNO dbs
to test_dbshelve.
........
r58445 | georg.brandl | 2007-10-13 06:20:03 -0700 (Sat, 13 Oct 2007) | 2 lines
Fix email example.
........
r58450 | gregory.p.smith | 2007-10-13 16:02:05 -0700 (Sat, 13 Oct 2007) | 2 lines
Fix an uncollectable reference leak in bsddb.db.DBShelf.append
........
r58453 | neal.norwitz | 2007-10-13 17:18:40 -0700 (Sat, 13 Oct 2007) | 8 lines
Let the O/S supply a port if none of the default ports can be used.
This should make the tests more robust at the expense of allowing
tests to be sloppier by not requiring them to cleanup after themselves.
(It will legitamitely help when running two test suites simultaneously
or if another process is already using one of the predefined ports.)
Also simplifies (slightLy) the exception handling elsewhere.
........
r58459 | neal.norwitz | 2007-10-14 11:30:21 -0700 (Sun, 14 Oct 2007) | 2 lines
Don't raise a string exception, they don't work anymore.
........
r58460 | neal.norwitz | 2007-10-14 11:40:37 -0700 (Sun, 14 Oct 2007) | 1 line
Use unittest for assertions
........
r58468 | armin.rigo | 2007-10-15 00:48:35 -0700 (Mon, 15 Oct 2007) | 2 lines
test_bigbits was not testing what it seemed to.
........
r58471 | guido.van.rossum | 2007-10-15 08:54:11 -0700 (Mon, 15 Oct 2007) | 3 lines
Change a PyErr_Print() into a PyErr_Clear(),
per discussion in issue 1031213.
........
r58500 | raymond.hettinger | 2007-10-16 12:18:30 -0700 (Tue, 16 Oct 2007) | 1 line
Improve error messages
........
r58506 | raymond.hettinger | 2007-10-16 14:28:32 -0700 (Tue, 16 Oct 2007) | 1 line
More docs, error messages, and tests
........
r58507 | andrew.kuchling | 2007-10-16 15:58:03 -0700 (Tue, 16 Oct 2007) | 1 line
Add items
........
r58508 | brett.cannon | 2007-10-16 16:24:06 -0700 (Tue, 16 Oct 2007) | 3 lines
Remove ``:const:`` notation on None in parameter list. Since the markup is not
rendered for parameters it just showed up as ``:const:`None` `` in the output.
........
r58509 | brett.cannon | 2007-10-16 16:26:45 -0700 (Tue, 16 Oct 2007) | 3 lines
Re-order some functions whose parameters differ between PyObject and const char
* so that they are next to each other.
........
r58522 | armin.rigo | 2007-10-17 11:46:37 -0700 (Wed, 17 Oct 2007) | 5 lines
Fix the overflow checking of list_repeat.
Introduce overflow checking into list_inplace_repeat.
Backport candidate, possibly.
........
r58530 | facundo.batista | 2007-10-17 20:16:03 -0700 (Wed, 17 Oct 2007) | 7 lines
Issue #1580738. When HTTPConnection reads the whole stream with read(),
it closes itself. When the stream is read in several calls to read(n),
it should behave in the same way if HTTPConnection knows where the end
of the stream is (through self.length). Added a test case for this
behaviour.
........
r58531 | facundo.batista | 2007-10-17 20:44:48 -0700 (Wed, 17 Oct 2007) | 3 lines
Issue 1289, just a typo.
........
r58532 | gregory.p.smith | 2007-10-18 00:56:54 -0700 (Thu, 18 Oct 2007) | 4 lines
cleanup test_dbtables to use mkdtemp. cleanup dbtables to pass txn as a
keyword argument whenever possible to avoid bugs and confusion. (dbtables.py
line 447 self.db.get using txn as a non-keyword was an actual bug due to this)
........
r58533 | gregory.p.smith | 2007-10-18 01:34:20 -0700 (Thu, 18 Oct 2007) | 4 lines
Fix a weird bug in dbtables: if it chose a random rowid string that contained
NULL bytes it would cause the database all sorts of problems in the future
leading to very strange random failures and corrupt dbtables.bsdTableDb dbs.
........
r58534 | gregory.p.smith | 2007-10-18 09:32:02 -0700 (Thu, 18 Oct 2007) | 3 lines
A cleaner fix than the one committed last night. Generate random rowids that
do not contain null bytes.
........
r58537 | gregory.p.smith | 2007-10-18 10:17:57 -0700 (Thu, 18 Oct 2007) | 2 lines
mention bsddb fixes.
........
r58538 | raymond.hettinger | 2007-10-18 14:13:06 -0700 (Thu, 18 Oct 2007) | 1 line
Remove useless warning
........
r58539 | gregory.p.smith | 2007-10-19 00:31:20 -0700 (Fri, 19 Oct 2007) | 2 lines
squelch the warning that this test is supposed to trigger.
........
r58542 | georg.brandl | 2007-10-19 05:32:39 -0700 (Fri, 19 Oct 2007) | 2 lines
Clarify wording for apply().
........
r58544 | mark.summerfield | 2007-10-19 05:48:17 -0700 (Fri, 19 Oct 2007) | 3 lines
Added a cross-ref to each other.
........
r58545 | georg.brandl | 2007-10-19 10:38:49 -0700 (Fri, 19 Oct 2007) | 2 lines
#1284: "S" means "seen", not unread.
........
r58548 | thomas.heller | 2007-10-19 11:11:41 -0700 (Fri, 19 Oct 2007) | 4 lines
Fix ctypes on 32-bit systems when Python is configured --with-system-ffi.
See also https://bugs.launchpad.net/bugs/72505.
Ported from release25-maint branch.
........
r58550 | facundo.batista | 2007-10-19 12:25:57 -0700 (Fri, 19 Oct 2007) | 8 lines
The constructor from tuple was way too permissive: it allowed bad
coefficient numbers, floats in the sign, and other details that
generated directly the wrong number in the best case, or triggered
misfunctionality in the alorithms.
Test cases added for these issues. Thanks Mark Dickinson.
........
r58559 | georg.brandl | 2007-10-20 06:22:53 -0700 (Sat, 20 Oct 2007) | 2 lines
Fix code being interpreted as a target.
........
r58561 | georg.brandl | 2007-10-20 06:36:24 -0700 (Sat, 20 Oct 2007) | 2 lines
Document new "cmdoption" directive.
........
r58562 | georg.brandl | 2007-10-20 08:21:22 -0700 (Sat, 20 Oct 2007) | 2 lines
Make a path more Unix-standardy.
........
r58564 | georg.brandl | 2007-10-20 10:51:39 -0700 (Sat, 20 Oct 2007) | 2 lines
Document new directive "envvar".
........
r58567 | georg.brandl | 2007-10-20 11:08:14 -0700 (Sat, 20 Oct 2007) | 6 lines
* Add new toplevel chapter, "Using Python." (how to install,
configure and setup python on different platforms -- at least
in theory.)
* Move the Python on Mac docs in that chapter.
* Add a new chapter about the command line invocation, by stargaming.
........
r58568 | georg.brandl | 2007-10-20 11:33:20 -0700 (Sat, 20 Oct 2007) | 2 lines
Change title, for now.
........
r58569 | georg.brandl | 2007-10-20 11:39:25 -0700 (Sat, 20 Oct 2007) | 2 lines
Add entry to ACKS.
........
r58570 | georg.brandl | 2007-10-20 12:05:45 -0700 (Sat, 20 Oct 2007) | 2 lines
Clarify -E docs.
........
r58571 | georg.brandl | 2007-10-20 12:08:36 -0700 (Sat, 20 Oct 2007) | 2 lines
Even more clarification.
........
r58572 | andrew.kuchling | 2007-10-20 12:25:37 -0700 (Sat, 20 Oct 2007) | 1 line
Fix protocol name
........
r58573 | andrew.kuchling | 2007-10-20 12:35:18 -0700 (Sat, 20 Oct 2007) | 1 line
Various items
........
r58574 | andrew.kuchling | 2007-10-20 12:39:35 -0700 (Sat, 20 Oct 2007) | 1 line
Use correct header line
........
r58576 | armin.rigo | 2007-10-21 02:14:15 -0700 (Sun, 21 Oct 2007) | 3 lines
Add a crasher for the long-standing issue with closing a file
while another thread uses it.
........
r58577 | georg.brandl | 2007-10-21 03:01:56 -0700 (Sun, 21 Oct 2007) | 2 lines
Remove duplicate crasher.
........
r58578 | georg.brandl | 2007-10-21 03:24:20 -0700 (Sun, 21 Oct 2007) | 2 lines
Unify "byte code" to "bytecode". Also sprinkle :term: markup for it.
........
r58579 | georg.brandl | 2007-10-21 03:32:54 -0700 (Sun, 21 Oct 2007) | 2 lines
Add markup to new function descriptions.
........
r58580 | georg.brandl | 2007-10-21 03:45:46 -0700 (Sun, 21 Oct 2007) | 2 lines
Add :term:s for descriptors.
........
r58581 | georg.brandl | 2007-10-21 03:46:24 -0700 (Sun, 21 Oct 2007) | 2 lines
Unify "file-descriptor" to "file descriptor".
........
r58582 | georg.brandl | 2007-10-21 03:52:38 -0700 (Sun, 21 Oct 2007) | 2 lines
Add :term: for generators.
........
r58583 | georg.brandl | 2007-10-21 05:10:28 -0700 (Sun, 21 Oct 2007) | 2 lines
Add :term:s for iterator.
........
r58584 | georg.brandl | 2007-10-21 05:15:05 -0700 (Sun, 21 Oct 2007) | 2 lines
Add :term:s for "new-style class".
........
r58588 | neal.norwitz | 2007-10-21 21:47:54 -0700 (Sun, 21 Oct 2007) | 1 line
Add Chris Monson so he can edit PEPs.
........
r58594 | guido.van.rossum | 2007-10-22 09:27:19 -0700 (Mon, 22 Oct 2007) | 4 lines
Issue #1307, patch by Derek Shockey.
When "MAIL" is received without args, an exception happens instead of
sending a 501 syntax error response.
........
r58598 | travis.oliphant | 2007-10-22 19:40:56 -0700 (Mon, 22 Oct 2007) | 1 line
Add phuang patch from Issue 708374 which adds offset parameter to mmap module.
........
r58601 | neal.norwitz | 2007-10-22 22:44:27 -0700 (Mon, 22 Oct 2007) | 2 lines
Bug #1313, fix typo (wrong variable name) in example.
........
r58609 | georg.brandl | 2007-10-23 11:21:35 -0700 (Tue, 23 Oct 2007) | 2 lines
Update Pygments version from externals.
........
r58618 | guido.van.rossum | 2007-10-23 12:25:41 -0700 (Tue, 23 Oct 2007) | 3 lines
Issue 1307 by Derek Shockey, fox the same bug for RCPT.
Neal: please backport!
........
r58620 | raymond.hettinger | 2007-10-23 13:37:41 -0700 (Tue, 23 Oct 2007) | 1 line
Shorter name for namedtuple()
........
r58621 | andrew.kuchling | 2007-10-23 13:55:47 -0700 (Tue, 23 Oct 2007) | 1 line
Update name
........
r58622 | raymond.hettinger | 2007-10-23 14:23:07 -0700 (Tue, 23 Oct 2007) | 1 line
Fixup news entry
........
r58623 | raymond.hettinger | 2007-10-23 18:28:33 -0700 (Tue, 23 Oct 2007) | 1 line
Optimize sum() for integer and float inputs.
........
r58624 | raymond.hettinger | 2007-10-23 19:05:51 -0700 (Tue, 23 Oct 2007) | 1 line
Fixup error return and add support for intermixed ints and floats/
........
r58628 | vinay.sajip | 2007-10-24 03:47:06 -0700 (Wed, 24 Oct 2007) | 1 line
Bug #1321: Fixed logic error in TimedRotatingFileHandler.__init__()
........
r58641 | facundo.batista | 2007-10-24 12:11:08 -0700 (Wed, 24 Oct 2007) | 4 lines
Issue 1290. CharacterData.__repr__ was constructing a string
in response that keeped having a non-ascii character.
........
r58643 | thomas.heller | 2007-10-24 12:50:45 -0700 (Wed, 24 Oct 2007) | 1 line
Added unittest for calling a function with paramflags (backport from py3k branch).
........
r58645 | matthias.klose | 2007-10-24 13:00:44 -0700 (Wed, 24 Oct 2007) | 2 lines
- Build using system ffi library on arm*-linux*.
........
r58651 | georg.brandl | 2007-10-24 14:40:38 -0700 (Wed, 24 Oct 2007) | 2 lines
Bug #1287: make os.environ.pop() work as expected.
........
r58652 | raymond.hettinger | 2007-10-24 19:26:58 -0700 (Wed, 24 Oct 2007) | 1 line
Missing DECREFs
........
r58653 | matthias.klose | 2007-10-24 23:37:24 -0700 (Wed, 24 Oct 2007) | 2 lines
- Build using system ffi library on arm*-linux*, pass --with-system-ffi to CONFIG_ARGS
........
r58655 | thomas.heller | 2007-10-25 12:47:32 -0700 (Thu, 25 Oct 2007) | 2 lines
ffi_type_longdouble may be already #defined.
See issue 1324.
........
r58656 | kurt.kaiser | 2007-10-25 15:43:45 -0700 (Thu, 25 Oct 2007) | 3 lines
Correct an ancient bug in an unused path by removing that path: register() is
now idempotent.
........
r58660 | kurt.kaiser | 2007-10-25 17:10:09 -0700 (Thu, 25 Oct 2007) | 4 lines
1. Add comments to provide top-level documentation.
2. Refactor to use more descriptive names.
3. Enhance tests in main().
........
r58675 | georg.brandl | 2007-10-26 11:30:41 -0700 (Fri, 26 Oct 2007) | 2 lines
Fix new pop() method on os.environ on ignorecase-platforms.
........
r58696 | neal.norwitz | 2007-10-27 15:32:21 -0700 (Sat, 27 Oct 2007) | 1 line
Update URL for Pygments. 0.8.1 is no longer available
........
r58697 | hyeshik.chang | 2007-10-28 04:19:02 -0700 (Sun, 28 Oct 2007) | 3 lines
- Add support for FreeBSD 8 which is recently forked from FreeBSD 7.
- Regenerate IN module for most recent maintenance tree of FreeBSD 6 and 7.
........
r58698 | hyeshik.chang | 2007-10-28 05:38:09 -0700 (Sun, 28 Oct 2007) | 2 lines
Enable platform-specific tweaks for FreeBSD 8 (exactly same to FreeBSD 7's yet)
........
r58700 | kurt.kaiser | 2007-10-28 12:03:59 -0700 (Sun, 28 Oct 2007) | 2 lines
Add confirmation dialog before printing. Patch 1717170 Tal Einat.
........
r58706 | guido.van.rossum | 2007-10-29 13:52:45 -0700 (Mon, 29 Oct 2007) | 3 lines
Patch 1353 by Jacob Winther.
Add mp4 mapping to mimetypes.py.
........
r58709 | guido.van.rossum | 2007-10-29 15:15:05 -0700 (Mon, 29 Oct 2007) | 6 lines
Backport fixes for the code that decodes octal escapes (and for PyString
also hex escapes) -- this was reaching beyond the end of the input string
buffer, even though it is not supposed to be \0-terminated.
This has no visible effect but is clearly the correct thing to do.
(In 3.0 it had a visible effect after removing ob_sstate from PyString.)
........
r58710 | kurt.kaiser | 2007-10-29 19:38:54 -0700 (Mon, 29 Oct 2007) | 7 lines
check in Tal Einat's update to tabpage.py
Patch 1612746
M configDialog.py
M NEWS.txt
AM tabbedpages.py
........
r58715 | georg.brandl | 2007-10-30 10:51:18 -0700 (Tue, 30 Oct 2007) | 2 lines
Use correct markup.
........
r58716 | georg.brandl | 2007-10-30 10:57:12 -0700 (Tue, 30 Oct 2007) | 2 lines
Make example about hiding None return values at the prompt clearer.
........
r58728 | neal.norwitz | 2007-10-30 23:33:20 -0700 (Tue, 30 Oct 2007) | 1 line
Fix some compiler warnings for signed comparisons on Unix and Windows.
........
r58731 | martin.v.loewis | 2007-10-31 10:19:33 -0700 (Wed, 31 Oct 2007) | 2 lines
Adding Christian Heimes.
........
r58737 | raymond.hettinger | 2007-10-31 14:57:58 -0700 (Wed, 31 Oct 2007) | 1 line
Clarify the reasons why pickle is almost always better than marshal
........
r58739 | raymond.hettinger | 2007-10-31 15:15:49 -0700 (Wed, 31 Oct 2007) | 1 line
Sets are marshalable.
........
2007-11-01 17:32:30 -03:00
|
|
|
For each entry in the table, a :term:`descriptor` will be constructed and added to the
|
2007-08-15 11:28:22 -03:00
|
|
|
type which will be able to extract a value from the instance structure. The
|
|
|
|
:attr:`type` field should contain one of the type codes defined in the
|
|
|
|
:file:`structmember.h` header; the value will be used to determine how to
|
|
|
|
convert Python values to and from C values. The :attr:`flags` field is used to
|
|
|
|
store flags which control how the attribute can be accessed.
|
|
|
|
|
|
|
|
The following flag constants are defined in :file:`structmember.h`; they may be
|
|
|
|
combined using bitwise-OR.
|
|
|
|
|
|
|
|
+---------------------------+----------------------------------------------+
|
|
|
|
| Constant | Meaning |
|
|
|
|
+===========================+==============================================+
|
|
|
|
| :const:`READONLY` | Never writable. |
|
|
|
|
+---------------------------+----------------------------------------------+
|
|
|
|
| :const:`READ_RESTRICTED` | Not readable in restricted mode. |
|
|
|
|
+---------------------------+----------------------------------------------+
|
|
|
|
| :const:`WRITE_RESTRICTED` | Not writable in restricted mode. |
|
|
|
|
+---------------------------+----------------------------------------------+
|
|
|
|
| :const:`RESTRICTED` | Not readable or writable in restricted mode. |
|
|
|
|
+---------------------------+----------------------------------------------+
|
|
|
|
|
|
|
|
.. index::
|
|
|
|
single: READONLY
|
|
|
|
single: READ_RESTRICTED
|
|
|
|
single: WRITE_RESTRICTED
|
|
|
|
single: RESTRICTED
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
An interesting advantage of using the :c:member:`~PyTypeObject.tp_members` table to build
|
2007-08-15 11:28:22 -03:00
|
|
|
descriptors that are used at runtime is that any attribute defined this way can
|
|
|
|
have an associated doc string simply by providing the text in the table. An
|
|
|
|
application can use the introspection API to retrieve the descriptor from the
|
|
|
|
class object, and get the doc string using its :attr:`__doc__` attribute.
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
As with the :c:member:`~PyTypeObject.tp_methods` table, a sentinel entry with a :attr:`name` value
|
2007-08-15 11:28:22 -03:00
|
|
|
of *NULL* is required.
|
|
|
|
|
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
........
2007-12-31 12:14:33 -04:00
|
|
|
.. XXX Descriptors need to be explained in more detail somewhere, but not here.
|
2009-01-03 17:18:54 -04: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
........
2007-12-31 12:14:33 -04:00
|
|
|
Descriptor objects have two handler functions which correspond to the
|
|
|
|
\member{tp_getattro} and \member{tp_setattro} handlers. The
|
|
|
|
\method{__get__()} handler is a function which is passed the descriptor,
|
|
|
|
instance, and type objects, and returns the value of the attribute, or it
|
|
|
|
returns \NULL{} and sets an exception. The \method{__set__()} handler is
|
|
|
|
passed the descriptor, instance, type, and new value;
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
|
|
|
|
Type-specific Attribute Management
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
For simplicity, only the :c:type:`char\*` version will be demonstrated here; the
|
|
|
|
type of the name parameter is the only difference between the :c:type:`char\*`
|
|
|
|
and :c:type:`PyObject\*` flavors of the interface. This example effectively does
|
2007-08-15 11:28:22 -03:00
|
|
|
the same thing as the generic example above, but does not use the generic
|
2008-07-02 19:59:48 -03:00
|
|
|
support added in Python 2.2. It explains how the handler functions are
|
2007-08-15 11:28:22 -03:00
|
|
|
called, so that if you do need to extend their functionality, you'll understand
|
|
|
|
what needs to be done.
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
The :c:member:`~PyTypeObject.tp_getattr` handler is called when the object requires an attribute
|
2007-08-15 11:28:22 -03:00
|
|
|
look-up. It is called in the same situations where the :meth:`__getattr__`
|
|
|
|
method of a class would be called.
|
|
|
|
|
|
|
|
Here is an example::
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
newdatatype_getattr(newdatatypeobject *obj, char *name)
|
|
|
|
{
|
2008-07-02 19:59:48 -03:00
|
|
|
if (strcmp(name, "data") == 0)
|
|
|
|
{
|
2015-02-17 04:18:44 -04:00
|
|
|
return PyLong_FromLong(obj->data);
|
2008-07-02 19:59:48 -03:00
|
|
|
}
|
|
|
|
|
|
|
|
PyErr_Format(PyExc_AttributeError,
|
|
|
|
"'%.50s' object has no attribute '%.400s'",
|
2009-01-03 17:31:47 -04:00
|
|
|
tp->tp_name, name);
|
2008-07-02 19:59:48 -03:00
|
|
|
return NULL;
|
2007-08-15 11:28:22 -03:00
|
|
|
}
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
The :c:member:`~PyTypeObject.tp_setattr` handler is called when the :meth:`__setattr__` or
|
2007-08-15 11:28:22 -03:00
|
|
|
:meth:`__delattr__` method of a class instance would be called. When an
|
|
|
|
attribute should be deleted, the third parameter will be *NULL*. Here is an
|
|
|
|
example that simply raises an exception; if this were really all you wanted, the
|
2013-08-01 16:12:45 -03:00
|
|
|
:c:member:`~PyTypeObject.tp_setattr` handler should be set to *NULL*. ::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
static int
|
|
|
|
newdatatype_setattr(newdatatypeobject *obj, char *name, PyObject *v)
|
|
|
|
{
|
|
|
|
(void)PyErr_Format(PyExc_RuntimeError, "Read-only attribute: \%s", name);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2009-03-31 15:56:38 -03:00
|
|
|
Object Comparison
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
::
|
|
|
|
|
|
|
|
richcmpfunc tp_richcompare;
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
The :c:member:`~PyTypeObject.tp_richcompare` handler is called when comparisons are needed. It is
|
2009-03-31 15:56:38 -03:00
|
|
|
analogous to the :ref:`rich comparison methods <richcmpfuncs>`, like
|
2010-10-06 07:11:56 -03:00
|
|
|
:meth:`__lt__`, and also called by :c:func:`PyObject_RichCompare` and
|
|
|
|
:c:func:`PyObject_RichCompareBool`.
|
2009-03-31 15:56:38 -03:00
|
|
|
|
|
|
|
This function is called with two Python objects and the operator as arguments,
|
|
|
|
where the operator is one of ``Py_EQ``, ``Py_NE``, ``Py_LE``, ``Py_GT``,
|
|
|
|
``Py_LT`` or ``Py_GT``. It should compare the two objects with respect to the
|
|
|
|
specified operator and return ``Py_True`` or ``Py_False`` if the comparison is
|
2010-09-21 11:48:28 -03:00
|
|
|
successful, ``Py_NotImplemented`` to indicate that comparison is not
|
2009-03-31 15:56:38 -03:00
|
|
|
implemented and the other object's comparison method should be tried, or *NULL*
|
|
|
|
if an exception was set.
|
|
|
|
|
|
|
|
Here is a sample implementation, for a datatype that is considered equal if the
|
|
|
|
size of an internal pointer is equal::
|
|
|
|
|
2013-04-12 10:08:40 -03:00
|
|
|
static PyObject *
|
2009-03-31 15:56:38 -03:00
|
|
|
newdatatype_richcmp(PyObject *obj1, PyObject *obj2, int op)
|
|
|
|
{
|
|
|
|
PyObject *result;
|
|
|
|
int c, size1, size2;
|
|
|
|
|
|
|
|
/* code to make sure that both arguments are of type
|
|
|
|
newdatatype omitted */
|
|
|
|
|
|
|
|
size1 = obj1->obj_UnderlyingDatatypePtr->size;
|
|
|
|
size2 = obj2->obj_UnderlyingDatatypePtr->size;
|
|
|
|
|
|
|
|
switch (op) {
|
|
|
|
case Py_LT: c = size1 < size2; break;
|
|
|
|
case Py_LE: c = size1 <= size2; break;
|
|
|
|
case Py_EQ: c = size1 == size2; break;
|
|
|
|
case Py_NE: c = size1 != size2; break;
|
|
|
|
case Py_GT: c = size1 > size2; break;
|
|
|
|
case Py_GE: c = size1 >= size2; break;
|
|
|
|
}
|
|
|
|
result = c ? Py_True : Py_False;
|
|
|
|
Py_INCREF(result);
|
|
|
|
return result;
|
|
|
|
}
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
|
|
|
|
Abstract Protocol Support
|
|
|
|
-------------------------
|
|
|
|
|
|
|
|
Python supports a variety of *abstract* 'protocols;' the specific interfaces
|
|
|
|
provided to use these interfaces are documented in :ref:`abstract`.
|
|
|
|
|
|
|
|
|
|
|
|
A number of these abstract interfaces were defined early in the development of
|
|
|
|
the Python implementation. In particular, the number, mapping, and sequence
|
|
|
|
protocols have been part of Python since the beginning. Other protocols have
|
|
|
|
been added over time. For protocols which depend on several handler routines
|
|
|
|
from the type implementation, the older protocols have been defined as optional
|
|
|
|
blocks of handlers referenced by the type object. For newer protocols there are
|
|
|
|
additional slots in the main type object, with a flag bit being set to indicate
|
|
|
|
that the slots are present and should be checked by the interpreter. (The flag
|
|
|
|
bit does not indicate that the slot values are non-*NULL*. The flag may be set
|
|
|
|
to indicate the presence of a slot, but a slot may still be unfilled.) ::
|
|
|
|
|
2012-09-28 11:34:45 -03:00
|
|
|
PyNumberMethods *tp_as_number;
|
|
|
|
PySequenceMethods *tp_as_sequence;
|
|
|
|
PyMappingMethods *tp_as_mapping;
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
If you wish your object to be able to act like a number, a sequence, or a
|
|
|
|
mapping object, then you place the address of a structure that implements the C
|
2010-10-06 07:11:56 -03:00
|
|
|
type :c:type:`PyNumberMethods`, :c:type:`PySequenceMethods`, or
|
|
|
|
:c:type:`PyMappingMethods`, respectively. It is up to you to fill in this
|
2007-08-15 11:28:22 -03:00
|
|
|
structure with appropriate values. You can find examples of the use of each of
|
|
|
|
these in the :file:`Objects` directory of the Python source distribution. ::
|
|
|
|
|
|
|
|
hashfunc tp_hash;
|
|
|
|
|
|
|
|
This function, if you choose to provide it, should return a hash number for an
|
|
|
|
instance of your data type. Here is a moderately pointless example::
|
|
|
|
|
|
|
|
static long
|
|
|
|
newdatatype_hash(newdatatypeobject *obj)
|
|
|
|
{
|
|
|
|
long result;
|
|
|
|
result = obj->obj_UnderlyingDatatypePtr->size;
|
|
|
|
result = result * 3;
|
|
|
|
return result;
|
|
|
|
}
|
|
|
|
|
|
|
|
::
|
|
|
|
|
|
|
|
ternaryfunc tp_call;
|
|
|
|
|
|
|
|
This function is called when an instance of your data type is "called", for
|
|
|
|
example, if ``obj1`` is an instance of your data type and the Python script
|
2013-08-01 16:12:45 -03:00
|
|
|
contains ``obj1('hello')``, the :c:member:`~PyTypeObject.tp_call` handler is invoked.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
This function takes three arguments:
|
|
|
|
|
|
|
|
#. *arg1* is the instance of the data type which is the subject of the call. If
|
|
|
|
the call is ``obj1('hello')``, then *arg1* is ``obj1``.
|
|
|
|
|
|
|
|
#. *arg2* is a tuple containing the arguments to the call. You can use
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:func:`PyArg_ParseTuple` to extract the arguments.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
#. *arg3* is a dictionary of keyword arguments that were passed. If this is
|
|
|
|
non-*NULL* and you support keyword arguments, use
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:func:`PyArg_ParseTupleAndKeywords` to extract the arguments. If you do not
|
2007-08-15 11:28:22 -03:00
|
|
|
want to support keyword arguments and this is non-*NULL*, raise a
|
|
|
|
:exc:`TypeError` with a message saying that keyword arguments are not supported.
|
|
|
|
|
|
|
|
Here is a desultory example of the implementation of the call function. ::
|
|
|
|
|
|
|
|
/* Implement the call function.
|
|
|
|
* obj1 is the instance receiving the call.
|
|
|
|
* obj2 is a tuple containing the arguments to the call, in this
|
|
|
|
* case 3 strings.
|
|
|
|
*/
|
|
|
|
static PyObject *
|
|
|
|
newdatatype_call(newdatatypeobject *obj, PyObject *args, PyObject *other)
|
|
|
|
{
|
|
|
|
PyObject *result;
|
|
|
|
char *arg1;
|
|
|
|
char *arg2;
|
|
|
|
char *arg3;
|
|
|
|
|
|
|
|
if (!PyArg_ParseTuple(args, "sss:call", &arg1, &arg2, &arg3)) {
|
|
|
|
return NULL;
|
|
|
|
}
|
2013-03-22 17:43:30 -03:00
|
|
|
result = PyUnicode_FromFormat(
|
2007-08-15 11:28:22 -03:00
|
|
|
"Returning -- value: [\%d] arg1: [\%s] arg2: [\%s] arg3: [\%s]\n",
|
|
|
|
obj->obj_UnderlyingDatatypePtr->size,
|
|
|
|
arg1, arg2, arg3);
|
|
|
|
return result;
|
|
|
|
}
|
|
|
|
|
2012-02-27 13:18:35 -04:00
|
|
|
::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
/* Iterators */
|
|
|
|
getiterfunc tp_iter;
|
|
|
|
iternextfunc tp_iternext;
|
|
|
|
|
|
|
|
These functions provide support for the iterator protocol. Any object which
|
|
|
|
wishes to support iteration over its contents (which may be generated during
|
|
|
|
iteration) must implement the ``tp_iter`` handler. Objects which are returned
|
|
|
|
by a ``tp_iter`` handler must implement both the ``tp_iter`` and ``tp_iternext``
|
|
|
|
handlers. Both handlers take exactly one parameter, the instance for which they
|
|
|
|
are being called, and return a new reference. In the case of an error, they
|
|
|
|
should set an exception and return *NULL*.
|
|
|
|
|
|
|
|
For an object which represents an iterable collection, the ``tp_iter`` handler
|
|
|
|
must return an iterator object. The iterator object is responsible for
|
|
|
|
maintaining the state of the iteration. For collections which can support
|
|
|
|
multiple iterators which do not interfere with each other (as lists and tuples
|
|
|
|
do), a new iterator should be created and returned. Objects which can only be
|
|
|
|
iterated over once (usually due to side effects of iteration) should implement
|
|
|
|
this handler by returning a new reference to themselves, and should also
|
|
|
|
implement the ``tp_iternext`` handler. File objects are an example of such an
|
|
|
|
iterator.
|
|
|
|
|
|
|
|
Iterator objects should implement both handlers. The ``tp_iter`` handler should
|
|
|
|
return a new reference to the iterator (this is the same as the ``tp_iter``
|
|
|
|
handler for objects which can only be iterated over destructively). The
|
|
|
|
``tp_iternext`` handler should return a new reference to the next object in the
|
|
|
|
iteration if there is one. If the iteration has reached the end, it may return
|
|
|
|
*NULL* without setting an exception or it may set :exc:`StopIteration`; avoiding
|
|
|
|
the exception can yield slightly better performance. If an actual error occurs,
|
|
|
|
it should set an exception and return *NULL*.
|
|
|
|
|
|
|
|
|
|
|
|
.. _weakref-support:
|
|
|
|
|
|
|
|
Weak Reference Support
|
|
|
|
----------------------
|
|
|
|
|
|
|
|
One of the goals of Python's weak-reference implementation is to allow any type
|
|
|
|
to participate in the weak reference mechanism without incurring the overhead on
|
|
|
|
those objects which do not benefit by weak referencing (such as numbers).
|
|
|
|
|
|
|
|
For an object to be weakly referencable, the extension must include a
|
2010-10-06 07:11:56 -03:00
|
|
|
:c:type:`PyObject\*` field in the instance structure for the use of the weak
|
2007-08-15 11:28:22 -03:00
|
|
|
reference mechanism; it must be initialized to *NULL* by the object's
|
2013-08-01 16:12:45 -03:00
|
|
|
constructor. It must also set the :c:member:`~PyTypeObject.tp_weaklistoffset` field of the
|
2007-08-15 11:28:22 -03:00
|
|
|
corresponding type object to the offset of the field. For example, the instance
|
|
|
|
type is defined with the following structure::
|
|
|
|
|
|
|
|
typedef struct {
|
|
|
|
PyObject_HEAD
|
|
|
|
PyClassObject *in_class; /* The class object */
|
|
|
|
PyObject *in_dict; /* A dictionary */
|
|
|
|
PyObject *in_weakreflist; /* List of weak references */
|
|
|
|
} PyInstanceObject;
|
|
|
|
|
|
|
|
The statically-declared type object for instances is defined this way::
|
|
|
|
|
|
|
|
PyTypeObject PyInstance_Type = {
|
2009-02-27 13:11:23 -04:00
|
|
|
PyVarObject_HEAD_INIT(&PyType_Type, 0)
|
2007-08-15 11:28:22 -03:00
|
|
|
0,
|
|
|
|
"module.instance",
|
|
|
|
|
|
|
|
/* Lots of stuff omitted for brevity... */
|
|
|
|
|
|
|
|
Py_TPFLAGS_DEFAULT, /* tp_flags */
|
|
|
|
0, /* tp_doc */
|
|
|
|
0, /* tp_traverse */
|
|
|
|
0, /* tp_clear */
|
|
|
|
0, /* tp_richcompare */
|
|
|
|
offsetof(PyInstanceObject, in_weakreflist), /* tp_weaklistoffset */
|
|
|
|
};
|
|
|
|
|
|
|
|
The type constructor is responsible for initializing the weak reference list to
|
|
|
|
*NULL*::
|
|
|
|
|
|
|
|
static PyObject *
|
|
|
|
instance_new() {
|
|
|
|
/* Other initialization stuff omitted for brevity */
|
|
|
|
|
|
|
|
self->in_weakreflist = NULL;
|
|
|
|
|
|
|
|
return (PyObject *) self;
|
|
|
|
}
|
|
|
|
|
|
|
|
The only further addition is that the destructor needs to call the weak
|
2012-06-15 14:11:31 -03:00
|
|
|
reference manager to clear any weak references. This is only required if the
|
|
|
|
weak reference list is non-*NULL*::
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
static void
|
|
|
|
instance_dealloc(PyInstanceObject *inst)
|
|
|
|
{
|
|
|
|
/* Allocate temporaries if needed, but do not begin
|
|
|
|
destruction just yet.
|
|
|
|
*/
|
|
|
|
|
|
|
|
if (inst->in_weakreflist != NULL)
|
|
|
|
PyObject_ClearWeakRefs((PyObject *) inst);
|
|
|
|
|
|
|
|
/* Proceed with object destruction normally. */
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
More Suggestions
|
|
|
|
----------------
|
|
|
|
|
|
|
|
Remember that you can omit most of these functions, in which case you provide
|
|
|
|
``0`` as a value. There are type definitions for each of the functions you must
|
|
|
|
provide. They are in :file:`object.h` in the Python include directory that
|
|
|
|
comes with the source distribution of Python.
|
|
|
|
|
|
|
|
In order to learn how to implement any specific method for your new data type,
|
2009-02-02 17:29:40 -04:00
|
|
|
do the following: Download and unpack the Python source distribution. Go to
|
|
|
|
the :file:`Objects` directory, then search the C source files for ``tp_`` plus
|
|
|
|
the function you want (for example, ``tp_richcompare``). You will find examples
|
|
|
|
of the function you want to implement.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
When you need to verify that an object is an instance of the type you are
|
2010-10-06 07:11:56 -03:00
|
|
|
implementing, use the :c:func:`PyObject_TypeCheck` function. A sample of its use
|
2007-08-15 11:28:22 -03:00
|
|
|
might be something like the following::
|
|
|
|
|
|
|
|
if (! PyObject_TypeCheck(some_object, &MyType)) {
|
|
|
|
PyErr_SetString(PyExc_TypeError, "arg #1 not a mything");
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
.. rubric:: Footnotes
|
|
|
|
|
|
|
|
.. [#] This is true when we know that the object is a basic type, like a string or a
|
|
|
|
float.
|
|
|
|
|
2013-08-01 16:12:45 -03:00
|
|
|
.. [#] We relied on this in the :c:member:`~PyTypeObject.tp_dealloc` handler in this example, because our
|
2007-08-15 11:28:22 -03:00
|
|
|
type doesn't support garbage collection. Even if a type supports garbage
|
|
|
|
collection, there are calls that can be made to "untrack" the object from
|
|
|
|
garbage collection, however, these calls are advanced and not covered here.
|
|
|
|
|
|
|
|
.. [#] We now know that the first and last members are strings, so perhaps we could be
|
|
|
|
less careful about decrementing their reference counts, however, we accept
|
|
|
|
instances of string subclasses. Even though deallocating normal strings won't
|
|
|
|
call back into our objects, we can't guarantee that deallocating an instance of
|
2008-03-16 14:29:44 -03:00
|
|
|
a string subclass won't call back into our objects.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
.. [#] Even in the third version, we aren't guaranteed to avoid cycles. Instances of
|
|
|
|
string subclasses are allowed and string subclasses could allow cycles even if
|
|
|
|
normal strings don't.
|