support for different event loops via asyncio

[jas-per]

currently pydbus has to use glib's mainloop - if you want to use pythons asyncio (trollius on python2) you have to run 2 event loops in your program. fortunately asyncio is designed to use different event loops underneath, so you can replace asyncio's event loop with the glib one by using https://github.com/nathan-hoad/gbulb and have all async code including pydbus run on glib's mainloop

a better solution for pydbus would be to use asyncio as event loop abstraction, so it could be used with any event loop underneath - in addition to the built-in asyncio event loop you can currently choose from uvloop, aiogevent (on top of gevent), tornado and glib

really appreciate the work you're doing for a modern pythonic dbus library - proper support for asyncio would help tremendously in establishing pydbus as the new standard lib for python/dbus

[hcoin]

I'm tinkering with the notion of expanding the dbus native 'signal' idea in an expanded pydbus implementation, which would enable the ideas above. See the fork hcoin/pydbus The working notion is: if any property or method call appends an '_async' then it completes immediately returning ever only 'none', with the timeout or completion or error noted in the arguments to function passed at bus.get time.

That, and named arguments. And defaults. And interpretation of bits in integers as tuples of string flags, and, bug fixes that allow pydbus to work on all the major distros, including publishing on glib versions prior to 2.46. All demonstrated with travis CI examples.

And... the novel notion that a dbus services can often be thought of as it's own ecosystem, one that uses argument names consistently within the namespace of a service. So... there's an option that supplies argument defaults from the last known value of that argument name in any use within that space.

That, and: result=dbuservice.method() --> say result position1 has name 'one'

result[1]==result.one==result['one']==result._arg_one == dbuservice._state.one

See much of it at https://github.com/hcoin/pydbus . I've got a big commit coming that implements the service-global argument-name-as-attribute space.

Pydbus is a great idea from Linus. My work is to make it possible for broad acceptance by doing much of the distro specific legwork and adding a few ideas.

[jas-per]

great to see so much work python/dbus going on, thanks a lot! I'm currently using https://github.com/ldo/dbussy for event-loop agnostic asyncio dbus, still a bit raw but very promising implemention! bit busy right now, but I'll definitely get more involved this fall/winter

[ldo]

You may not need to do anything. Try glibcoro to provide the asyncio wrapper for the GLib event loop, and pydbus should be able to work with asyncio-using code unchanged.

[tenuki]

You may not need to do anything. Try glibcoro to provide the asyncio wrapper for the GLib event loop, and pydbus should be able to work with asyncio-using code unchanged.

Cool, but, glibcoro refers to gbulb like being the same but more advanced.. and gbulb is unmaintained.. :-(