After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 626234 - Migrate from PyGTK to PyGObject introspection-based bindings
Migrate from PyGTK to PyGObject introspection-based bindings
Product: sabayon
Classification: Deprecated
Component: general
SVN trunk
Other Linux
: Normal normal
: ---
Assigned To: Maintainers of sabayon
Maintainers of sabayon
Depends on:
Blocks: 626218
Reported: 2010-08-06 16:28 UTC by André Klapper
Modified: 2014-08-02 12:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32

Description André Klapper 2010-08-06 16:28:58 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 for more information and guidelines.

For help there is a mailing list at . For getting involved in the development of pygobject there is a mailing list at . There is also the #python IRC channel on

./sabayon/, gdk-x11-2.0 pygobject-2.0 pygtk-2.0)
Comment 1 André Klapper 2011-01-17 21:04:08 UTC
[Removing 3.0 target as this is not a hard blocker, but a nice to have]
Comment 2 André Klapper 2014-08-02 12:12:48 UTC
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.