GNOME Bugzilla – Bug 626242
Migrate from PyGTK to PyGObject introspection-based bindings
Last modified: 2018-05-24 12:49:53 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. ./gimp/configure.ac: PKG_CHECK_MODULES(PYGTK, pygtk-2.0 >= pygtk_required_version,,
BUMP and Confirmed PyGTK 2.24.0 has been released. This is a stable release supporting the GTK+ 2.24 API. New users wishing to develop Python applications using GTK+ are recommended to use the GObject-Introspection features available in PyGObject. Existing authors of PyGTK applications are also recommended to port their applications to PyGObject to take advantage of new features appearing in GTK-3 and beyond. More information on PyGObject and GObject-Introspection can be found at http://live.gnome.org/PyGObject. PyGTK-2.24 will be the final major release of PyGTK. Additional bug-fix releases may appear when necessary to maintain compatibility and stability with the GTK-2.24 series. ---- Additional Notes...PyGTK 2.24 will not build on Snow Leopard. Therefore GIMP will not build with python and therefore is useless (for me) since I need python to use the plugins I have. How much work on this has been done already and when can it get merged to git master? Thanks, Jeff
Hi Jeff, I assume that you are going to provide the patches? Nobody is currently working on the python extension.
I cannot provide patches as I am not a developer. I am more of a power user that can fix some code here and there. Porting from PyGTK to PyGobject would be out of my league. Why is this not more of a priority...Is Python-fu not a heavily used plugin system for GIMP? Am I the only one that still uses python-based plugins for GIMP?
It's not a priority because the around 3.5 active developers have more important things to do, like keeping GIMP running at all.
Yep...free doesn't pay like it used to. I guess I will do without for now.
Do you confirm it does not work on Mac OS X as it is today? That would make this a regression bug that could be dealt with along the GIMP 2.8 life cycle (since there won't be API changes for the user plug-ins themselves) (I should start working on this, but it was my intention to update the whole gimp-python for GIMP 2.10)
This will likely imply changing GIMP Python to use GTK+3.x as well - and with such changes in the way, there is no motive not to change to Python3 while at it. Would anyone be impaired with GIMP-Python using gtk+3? I used to be worried about Windows installers having to ship both gtk+3 and gtk+2 (for GIMP itself), but it seems they already do it.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/339.