GNOME Bugzilla – Bug 626246
Migrate from PyGTK to PyGObject introspection-based bindings
Last modified: 2020-11-08 13:17:07 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. ./gcompris/configure.ac: PKG_CHECK_MODULES(PYGTK, pygtk-2.0 pycairo)
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. Furthermore, GCompris development has moved to a different platform (from GTK+ to Qt). The last legacy release based on GTK+ was version 15.10 in October 2015. If you can still reproduce this problem in a recent and supported of GCompris, then please feel free to report it at https://bugs.kde.org/buglist.cgi?product=gcompris See https://gcompris.net/ for more information. Thank you for reporting this issue and we are sorry it could not be fixed.