python - using a signal not in introspection
John (J5) Palmieri
johnp at redhat.com
Thu Apr 26 09:31:41 PDT 2007
On Thu, 2007-04-26 at 12:08 -0400, Havoc Pennington wrote:
> Hi,
>
> John (J5) Palmieri wrote:
> > Figured it out. For some reason the new bindings do not spit out an
> > error message when a signal does not match the number of arguments
> > listed. To deal with this you can do
> >
> > def __on_action(self, *args):
>
> Does not work for me with 0.70 anyway. I'll append the test case.
>
> > What is libnotify supposed to be sending back because as far as I can
> > tell it does not send back a notify_id though I am guessing it should.
> >
>
> From what I can tell the args are supposed to be a notify id and an
> action name.
>
> Havoc
>
> #! /usr/bin/python
>
> import dbus, gobject
import dbus.glib #adds mainloop integration.
Simon had made this explicit in git I believe (though import dbus.glib
should work too) and has also added errors if you try to do something
like connect to a signal without having a mainloop.
--
John (J5) Palmieri <johnp at redhat.com>
More information about the dbus
mailing list