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 626237 - Migrate from PyGTK to PyGObject introspection-based bindings
Migrate from PyGTK to PyGObject introspection-based bindings
Status: RESOLVED DUPLICATE of bug 598536
Product: pygtksourceview
Classification: Bindings
Component: general
Git Master
Other Linux
: Normal normal
: ---
Assigned To: pygtksourceview-maint
Depends on:
Blocks: 626218
 
 
Reported: 2010-08-06 16:30 UTC by André Klapper
Modified: 2011-09-06 21:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


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

./pygtksourceview/configure.ac:        pygtk-2.0 >= pygtk_required_version
Comment 1 Javier Jardón (IRC: jjardon) 2011-09-06 21:40:02 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 598536 ***