Hello Georges, Georges Khaznadar [2014-03-05 18:44 +0100]: > So, which way would you approve? > [...] > 3- or some other approach?
Ah, I thought I already pointed that out in my initial bug report: The existing libudisks is introspectable, so there are "automatic" bindings to it using python[3]-gi and gir1.2-udisks-2.0. udisks2's own test suite uses those: http://cgit.freedesktop.org/udisks/tree/src/tests/integration-test usb-creator is another example of talking to udisks2 through introspection: http://bazaar.launchpad.net/~usb-creator-hackers/usb-creator/trunk/view/head:/usbcreator/backends/udisks/backend.py This is a general description of what GI does: https://wiki.gnome.org/Projects/GObjectIntrospection This is an overview of how a C API like libudisks translates to a Python API using python-gi: https://wiki.gnome.org/Projects/PyGObject/IntrospectionPorting#How_does_PyGI_work.3F Otherwise, if you don't like this, you can of course still talk to udisks2 through D-BUS in much the same way and structure as scolasync currently does to udisks1. Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
