delta/dbus-python.git/_dbus_bindings/message.c, branch dbus-python-1.1.1

Use native 'int' (whatever that means) for variant_level etc.

2012-01-11T15:03:08+00:00

This reverts the Python 2 API to be in terms of PyInt, leaving the
Python 3 API in terms of PyLong (which is called 'int' in Python code).

Consistently use the str type for identifier-like (ASCII) strings

2012-01-11T12:57:15+00:00

Porting to Python 3 left these methods returning unicode, which is
arguably an API break in Python 2:

* Message.get_member
* Message.get_path_decomposed (array of unicode)
* Message.get_sender
* Message.get_destination
* Message.get_interface
* Message.get_error_name
* Server.get_address
* Server.get_id

Instead, make them return whatever the natural str type is (bytes in
Python 2, unicode in Python 3).

SignalMessage.repr: include the destination and abbreviate "interface" more conventionally

2012-01-11T12:50:43+00:00

Yes, signals can have a destination. The default is to broadcast.

This is the big one; it adds Python 3 support.

2011-12-15T11:57:21+00:00

First round of PyInt -> PyLong changes. These are only compatible with Python

2011-12-14T20:05:16+00:00

2, since there are still some unconditional PyInt calls, which are not valid
in Python 3.  However, it lays the framework for conditionalizing on Python 3
and using only PyLong in that case.  Where it doesn't matter, PyLong is used
unconditionally.

In preparation for Python 3 support, use the Python 2 PyBytes aliases for the

2011-12-14T18:36:39+00:00

PyString API.  This makes the code compilable in Python 2.x (x >= 6) and
Python 3.

Additional PyObject_HEAD_INIT -> PyVarObject_HEAD_INIT changes in preparation

2011-12-13T21:21:04+00:00

for Python 3 support.

Use Py_TYPE() rather than thing->ob_type, for Python 3 portability

2011-12-13T11:38:48+00:00

Based on part of a patch from Barry Warsaw.

Signed-off-by: Simon McVittie

fd.o #23831: make sure to ref types passed to PyModule_AddObject

2010-12-02T17:27:34+00:00

This avoids these static types wrongly being deallocated. Python
implements static types as having one initial reference, which is never
meant to be released, but if you get your refcounting wrong they'll be
"deallocated" (causing a crash) during Py_Finalize.

Use Py_CLEAR for greater robustness

2010-12-02T16:31:07+00:00