February 2010


For those of you who haven’t seen Tomeu Vizoso’s blog on the hackfest we are trying to pull together this is a second call to PyGObject, Python 3 and GtkIntrospect hackers who might want to join us in getting the future of the Python bindings to GTK sorted out.

At issue are a couple of roadblocks to the continual maintenance of the the bindings. First is the lack of support for Python 3.0 and second is the unclear picture of how GNOME 3 effects us. The current plan is to finish the work done on PyGI (Python GObjectIntrospect support for PyGObject), at the same time making sure it all works under both Python 2.x and Python 3.x. Moving to the PyGI bindings should make the maintenance burden somewhat lighter for our busy maintainers.

If you have something you can contribute and are interested in attending our hackfest please take a look at the wikipage and e-mail myself or Tomeu. While this is being sponsored by the GNOME Foundation, you don’t need to be a Foundation member to be considered for an invite. We hope to be finalizing things soon and getting a budget to send to the board for approval.

[read this post in: ar de es fr it ja ko pt ru zh-CN ]

Well, I’ve gone and done it. Thanks to David Malcolm’s excellent 2to3c tool and some hand wrangling with PyUnicode objects I was able to get D-Bus Python compiling and working on Python 3. Grab the patch and start testing it out.

I’ve also tested this under Python 2.6 but it would be nice to see if it also works under Python versions < 2.6 since 2.6 has a couple of compatibility layers built in.

[read this post in: ar de es fr it ja ko pt ru zh-CN ]