Comment 54 for bug 893091

To clear things up further, we are not forcing people to use GLib integration. It is up to KDE and Qt people to decide how they want to support D-Bus in python. There are plenty of options here, the GLib integration being one of them.

What happened was I no longer work on D-Bus. Any work I do in that area is purely because I see a need and take time out to lend my knowledge to the situation. I wrote the Py3k branch because we were making a push for Py3k support in Fedora and upstream GNOME. When I realized we needed the glib mainloop in pygobject to be ported to py3k to run the complete test suite I switched focus to that.

We decided in that project to switch from statically binding APIs to using the new GObject Introspection libraries. That almost instantly opened up the GDBus API to python. A small shim was written by Martin Pitti to bring some of the nicer syntax from DBus-Python. It means less maintenance for us in the long run as well as better resource usage.

In any case while it would be nice to support a generic library for D-Bus in Python 3, the parts that I had time for are already solved on my end. I'm sure Simon, with everything that is on his plate, is in the same position.

I've already done most of the heavy lifting to porting this library to Py3k. So there are options for Qt support when moving to Python 3. Someone just has to step up to the plate and spend the time on it to the level that the past maintainers have already put in (e.g. you can't just code dump and walk away, someone needs to support this). DBus-Python will still work and be supported for some time to come under Python 2. Let's not start bike-shedding the issue.