Get your pygobject patches here, fresh off my local git tree. All pertinent tests pass in Python 2 & 3 and we are just waiting on reviews to confirm this. All that is needed is to split out the generated gio bindings and I think we can do another solid pygobject release – now Python 3 introspection enabled for a brighter, whiter smile.
Does this mean that the Python 3 port is done?
Probably not. I’m sure people will find bugs that we will need to fix but, it passes all the tests and that means we can get it to a wider audience. It does mean I can move to more of the higher level bits that still need fixing up for a smooth transition between PyGTK/Gtk2 and PyGI/Gtk3.
[read this post in: ar de es fr it ja ko pt ru zh-CN ]
Does pygi cover cairo too ?
Comment by Stu — September 14, 2010 @ 5:17 pm
Ah, you reminded me that I still need to find out if PyCairo is ported to Python 3. We support pycairo through the foreign types system. That means that we have cairo support and can pass around cairo objects to Gdk API that needs them but we rely on PyCairo for any operations on those objects in python. So if it isn’t ported then I’ll have to look at that next.
Comment by J5 — September 14, 2010 @ 5:26 pm
From lurking on the mailinglist I think it is (the python 2 version is now py2cairo) but there are no bindings for 1.10 yet.
Comment by Stu — September 14, 2010 @ 5:35 pm
Thanks for all your great work on this.
Comment by andre — September 15, 2010 @ 3:54 am
So I got pycairo compiling under py3k (it was a bit harder than it should be). In any case it works and passes the pygi tests.
Comment by J5 — September 16, 2010 @ 10:14 am