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 626250 - gedit-bugreport.sh.in: Migrate from PyGTK to PyGObject introspection-based bindings
gedit-bugreport.sh.in: Migrate from PyGTK to PyGObject introspection-based bi...
Status: RESOLVED FIXED
Product: gedit
Classification: Applications
Component: general
git master
Other Linux
: Normal enhancement
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks: 626218
 
 
Reported: 2010-08-06 16:37 UTC by André Klapper
Modified: 2011-03-14 16:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Description André Klapper 2010-08-06 16:37:18 UTC 
Gedit uses PyGTK in /data/gedit-bugreport.sh.in.

As it is unlikely that anybody will continue maintaining the PyGTK 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.
Comment 1 Steve Frécinaux 2010-08-06 16:42:51 UTC 
Is this script still being used by anyone? It was used by bugbuddy but I don't know what's the state of it now.
Comment 2 André Klapper 2011-01-17 21:04:13 UTC 
[Removing 3.0 target as this is not a hard blocker, but a nice to have]
Comment 3 Ignacio Casal Quinteiro (nacho) 2011-03-14 16:29:57 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.