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 626238 - GNOME Goal: Migrate from PyGTK to PyGObject introspection-based bindings
GNOME Goal: Migrate from PyGTK to PyGObject introspection-based bindings
Status: RESOLVED OBSOLETE
Product: planner
Classification: Other
Component: General
unspecified
Other All
: Normal normal
: ---
Assigned To: planner-maint
planner-maint
cleanup
Depends on:
Blocks: 626218
 
 
Reported: 2010-08-06 16:30 UTC by André Klapper
Modified: 2021-06-09 20:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Description André Klapper 2010-08-06 16:30:36 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.

./planner/configure.in:      PKG_CHECK_MODULES(PYGTK, pygtk-2.0 >= $PYGTK_REQUIRED, have_python=yes, have_python=no)
Comment 1 GNOME Infrastructure Team 2021-06-09 20:44:37 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/World/planner/-/issues/195.