GNOME Bugzilla – Bug 626229
Migrate from PyGTK to PyGObject introspection-based bindings
Last modified: 2010-08-06 17:26:23 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. ./gtk-vnc/configure.ac: PKG_CHECK_MODULES(PYGTK, pygtk-2.0 >= $PYGTK_REQUIRED)
GTK-VNC already provides GObject introspection data for its APIs. eg this example using GJS/Seed http://git.gnome.org/browse/gtk-vnc/tree/examples/gvncviewer.js The PyGTK2 based binding is kept for backwards compatibility. If you build GTK-VNC against GTK3, then the legacy binding will be explicitly disabled: http://mail.gnome.org/archives/gtk-vnc-list/2010-July/msg00019.html Unless there's something extra required for PyGObject beyond just providing GIR data, then this can be closed
Oh great. Thanks a lot for explaining!