[patch] raise exceptions when you try to use python bindings without a mainloop

[John (J5) Palmieri]

The tough thing here is that I might add a generic main loop but there
is no way to tell that the generic mainloop driver is loaded but the
user used the glib mainloop.  More grr moments to come :-)  What I will
do is not add the generic mainloop automatically.  This way a user will
have to explicitly load it and will hopefully know they have to use that
mainloop.   The only other place this make sense is if the user does
pending calls but perhaps in those situations we should spit out a
warning and then convert it into a blocking call.  I'm not sure.

On Tue, 2005-10-04 at 12:26 +0100, Robert McQueen wrote:
> I've run into this "why don't I get any signals? grr!" and so has
> someone on #dbus, so I guess it's worth adding a check. This throws an
> exception when you try to bind to a signal and don't have a mainloop
> binding like dbus.glib loaded. It might make sense to also error when
> you try and make method calls too, not certain.
> 
> Regards,
> Rob
> _______________________________________________
> dbus mailing list
> dbus at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dbus

-- 
John (J5) Palmieri <johnp at redhat.com>