GNOME Bugzilla – Bug 626244
Migrate from PyGTK to PyGObject introspection-based bindings
Last modified: 2019-02-22 03:17:03 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. ./eog-plugins/configure.ac: pygtk-2.0 >= $PYGTK_REQUIRED],
...or maybe it makes more sense for the plugin part to consider libpeas.
(In reply to comment #1) > ...or maybe it makes more sense for the plugin part to consider libpeas. Yup, that's the plan (bug 626091). So, the plugins will need to be reworked anyway.
I'm already working on this. By now I have eog with introspection ready, but I still need to make the python plugins work.
Just for reference: Python plugins for eog are currently not supported until bug 639597 is fixed. There's also just two plugins affected in eog-plugins by this: Slideshow Shuffle and the Python Console (can possibly synced with the corresponding gedit extension)
This is also fixed in 3.0. The python has been activated in time for that release and the python plugins in the eog-plugins have been migrated to the new API. This problem has been fixed in our software repository. The fix has gone into the last software release. Thank you for your bug report.