GNOME Bugzilla – Bug 626247
Migrate from PyGTK to PyGObject introspection-based bindings
Last modified: 2011-08-31 11:17:20 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. ./emerillon-plugins/configure.ac: pygtk-2.0 >= $PYGTK_REQUIRED],
Migration to libpeas is planned for emerillon, so this is also on my TODO list.
I did the migration to libpeas in the "gtk3" branch. As a proof I ported the search plugin. The other plugins still need to be done but I guess that's pretty trivial.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.