GObject - why dragging in such a huge dependency only for its mainloop?
mirko opened this issue · 3 comments
mirko commented
Hello!
I wonder about why GObject is a dependency and apparently the only place where GObject is actually used, is gatt/gatt_linux.py:89: self._main_loop = GObject.MainLoop()
.
As PyGObject also requires GObject-introspection that's a huge I dependency and I wonder what's so special about its mainloop.
If I'm allowed to wish, I'd love to see this dependency gone, however - as I said - there might be good reasons I don't yet understand. Either way, I'd appreciate to understand what's so special about GObject's mainloop.
mirko commented
nope
Deleted user commented
It works fine with self._main_loop = dbus.mainloop.glib.DBusGMainLoop
and without GObject
as dependency.