Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GObject - why dragging in such a huge dependency only for its mainloop? #29

Open
mirko opened this issue Mar 19, 2018 · 3 comments
Open

Comments

@mirko
Copy link

mirko commented Mar 19, 2018

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.

@Snevzor
Copy link

Snevzor commented Mar 21, 2019

Hello @mirko,

Do you have some updated information on this matter perhaps?

@mirko
Copy link
Author

mirko commented Mar 24, 2019

nope

@ghost
Copy link

ghost commented May 22, 2019

It works fine with self._main_loop = dbus.mainloop.glib.DBusGMainLoop and without GObject as dependency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants