GNOME Bugzilla – Bug 626234
Migrate from PyGTK to PyGObject introspection-based bindings
Last modified: 2014-08-02 12:12:48 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.
./sabayon/configure.ac:PKG_CHECK_MODULES(XLIB_MODULE, gdk-x11-2.0 pygobject-2.0 pygtk-2.0)
[Removing 3.0 target as this is not a hard blocker, but a nice to have]
The last Sabayon code changes took place in February 2010:
This project is not under active development anymore.
This project has been recently archived in GNOME Git.
It is currently unlikely that there will be any further active development.
Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.