[dbus-python] signal filtering bug?

Wladimir van der Laan laanwj at gmail.com
Wed Dec 20 00:50:23 PST 2006

Is this a dbus-python specific limitation or one to DBus as a whole?

Could you give a pointer as to where to get started on implementing
this? Of course I could simply use strings now that I know this, but
it seems ackward to change my API just to get around a missing
implementation detail.

On 12/19/06, Havoc Pennington <hp at redhat.com> wrote:
> Wladimir van der Laan wrote:
> > Now the surprise: when I comment out section A, so to receive only
> > events with arg0=147, *nothing* is received at all. Even though all
> > the signals have arg0=147.
> It's a documented limitation - the argN signal match rules only work on
> arguments of type string. Integers won't be matched (unless they are
> sent as strings).
> This would be worth fixing, just a matter of coding.
> Havoc

Ogre3D Team (http://www.ogre3d.org)

More information about the dbus mailing list