GNOME Bugzilla – Bug 626233
Migrate from PyGTK to PyGObject introspection-based bindings
Last modified: 2013-01-15 22:43:33 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.
./pessulus/configure.ac:PKG_CHECK_MODULES([PESSULUS], [pygtk-2.0 >= 2.13.0])
[Removing 3.0 target as this is not a hard blocker, but a nice to have]
We are sorry, but pessulus will no longer be maintained due to lack of manpower. I am closing all remaining open bug reports. Pessulus is already closed down for new report submissions.
Apologies for the noise and any inconvenience caused by it.