GNOME Bugzilla – Bug 626254
Migrate from PyGTK to PyGObject introspection-based bindings
Last modified: 2011-08-30 01:57:37 UTC
Grep'ing for pygtk-2.0 it seems that this module uses the stable bindings provided by PyGTK.
As it is unlikely that anybody will continue maintaining these stable bindings, applications using PyGTK should be ported to using the dynamic Python bindings provided by PyGObject (now that PyGI has been merged into PyGObject).
The feedback on migration provided by application maintainers will also help PyGObject to improve its dynamic bindings.
Please see http://live.gnome.org/GnomeGoals/PythonIntrospectionPorting for more information and guidelines.
For help there is a mailing list at http://www.daa.com.au/mailman/listinfo/pygtk . For getting involved in the development of pygobject there is a mailing list at http://mail.gnome.org/mailman/listinfo/python-hackers-list . There is also the #python IRC channel on irc.gimp.net.
./README:* pygtk - GTK+ Python bindings
./configure.in:AM_CHECK_PYGTK(2.0,,[AC_MSG_ERROR(Could not find pygtk 2.0)])
[Removing 3.0 target as this is not a hard blocker, but a nice to have]
The team's decision to maintain two 'unstable' branches in Orca, while more work for us, would seem to have some happy side effects including <drum roll please>: We just eliminated any need to have a single Orca branch which could support both PyGTK and PyGObject Introspection.
As a result, what was a rather mammoth task, is now just a large, tedious one. ;-) I'm down with that. :-)
Bumping this one up on my to-do list. 3.1.3 at the latest, maybe even by 3.1.2 if the Fates are feeling charitable.
The Fates are clearly not feeling charitable. See bug 653588.
With bug 657120, Orca hangs if a key is pressed.
We can open new bugs for the various issues we'll undoubtedly find.