I have a little over 15 tests still failing in the pygobject under python 3 and they are now mostly localized to the gi module. That is great compared to the 50 or so tests I had failing yesterday. It is even greater when one considers that the bulk of the failed tests have to do with PyLong to C long conversions. Most likely those are places where we did a quick conversion to make it compile under py3k but now need just a little more thought on how we are handling numbers. There are still a couple more obscure bugs that look like everything is happening correctly in C but the wrong value is shown in python.
In any case, we are pushing to be able to release along side Gnome 3 at the end of the year and I think we are on track. I would like to finish up the python 3 port soon so I can get back to fixing up annotation in Gtk and helping port apps before we do the release. I suspect the bulk of my work after the release will be porting the remaining apps and helping make sure libraries are ported to use GObject Introspection where appropriate.
Update: six more tests to go, though they are a bit more obscure than the others
[read this post in: ar de es fr it ja ko pt ru zh-CN ]
John, I would like to thank you so much for working on this! It was a tough bullet to take and you’ve done a outstanding work not only by sitting down and doing work, but also leading the rest of the PyGTK community to push to get to where we are.
Make sure to demand me a beer next time we meet!
Comment by Alberto Ruiz — September 9, 2010 @ 3:58 pm
Thanks a lot for your efforts!
Comment by Sebastian Heinlein — September 10, 2010 @ 12:54 am
Hey J5, I think I love you
Your hard work is very much appreciated!
Comment by Mikkel Kamstrup Erlandsen — September 10, 2010 @ 3:04 am
Alberto is spot-on.
By the way, where’s the flattr button?
Comment by Tshepang Lekhonkhobe — September 10, 2010 @ 4:39 am
Just to be sure: will there still be Python 2 support for GTK?
Comment by oliver — September 10, 2010 @ 8:37 am
I also want to thank your great work as a PyGTK (and future pygojbect) developer. Read you by the mailing list -I guess.
Comment by jors — September 11, 2010 @ 2:33 pm
Thanks all for the words of encouragement.
@oliver –
PyGTK will remain Python 2 compliant but will not be moved to Python 3 and will most likely not be ported to Gnome 3.0
pygobject using gobject-introspection will be supported under Python 3.x and will fully wrap Gtk 3. We will try to keep compatibility for Python 2 but that is not a guarantee if they start to diverge too much. For now it is pretty easy. We also can not fully remain compatible with Gtk 2 due to a number of API’s that can not be wrapped safely. Such API’s like the Gdk.Style structures have not way of being accessed through introspection. In Gtk 3 API like that goes away and places which we still need to read from structs should have accessor functions.
I should note that PyGTK not supporting Gtk 3 is totally up to someone coming in and continuing to add wrappers for all the new API. It is doable but the main python team thinks it is not worth the effort. We belive that keeping PyGTK stable for Gtk 2/python 2 is very important and that moving forward, the Gtk3/Python 3 support for pygobject is the way forward. Even if PyGTK was able to get support for Gtk 3 it will always lag behind since pygobject will get the changes as soon as the new Gtk+ is released.
Comment by J5 — September 12, 2010 @ 10:47 am