Python binding: ProxyObject questions

[Jeroen T. Vermeulen]

On Thu, August 24, 2006 23:37, John (J5) Palmieri wrote:

> I wrote it as a cast, so you cast the proxy to the interface.  The other
> way of doing it is proxy.method(dbus_interface="...")

A cast sounds like a nice trick.  From what I can see so far there's just
no way to add Python methods to a proxy that would be guaranteed not to
clash with the dbus object's methods...

Does the name-clash problem exist also with dbus methods having parameters
called "dbus_interface," by the way?


> It is a holdover from the way old bindings.  I had a good answer for why
> it doesn't clash at one point.  I can't remember it now.  I don't
> recommend that API in any case since the service has to be running in
> order to connect to the signal.  The python bindings are due for an
> overhaul.  Jdahlin wants to change them completely.

I was about to document the basics of the Python API in my new tutorial...
 Do you think it would be better to hold off on that?


Jeroen