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 632113 - Migrate from PyGTK to PyGObject introspection-based bindings
Migrate from PyGTK to PyGObject introspection-based bindings
Product: pitivi
Classification: Other
Component: General
Other GNU Hurd
: High normal
: 0.91
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on: 600688 646788 648015 677013 679757 680913 681139
Blocks: 626218 679758
Reported: 2010-10-14 01:36 UTC by Javier Jardón (IRC: jjardon)
Modified: 2012-09-02 04:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Javier Jardón (IRC: jjardon) 2010-10-14 01:36:54 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 for more
information and guidelines.

For getting involved in the development of pygobject there is a mailing list at
There is also the #python IRC channel on
Comment 1 John Stowers 2010-10-14 11:22:41 UTC
Javier, your message is not quite correct - I will continue to maintain PyGTK and support the GTK+-2.X API.
Comment 2 André Klapper 2010-10-14 11:42:50 UTC
John: Via static bindings?
Comment 3 John Stowers 2010-10-14 20:48:57 UTC
Yeah, I'm maintaining the PyGTK static bindings now.

No new gtk+-3.0 features will be added to PyGTK but for the last (2.22) release I finished updating the PyGTK bindings so they now cover the complete 2.X API.

In future I will be making bug fix releases and ensuring that PyGTK continues to work against gtk+-2.X.
Comment 4 Maël Lavault 2011-06-08 11:43:39 UTC
By the way, you will have to wait for goocanvas to add support of gobject introspection, this is a work in progress.
Comment 5 John Stowers 2011-06-08 13:36:23 UTC
(In reply to comment #4)
> By the way, you will have to wait for goocanvas to add support of gobject
> introspection, this is a work in progress.

Check the dependent bug 648015 , I'm working on the goocanvas introspection ATM. I expect it actually works well enough for Pitivi to use it now.
Comment 6 Jean-François Fortin Tam 2012-07-11 15:09:22 UTC
Still in the plans, but that'll take a while. We might end up using the compatibility layer for gtk, unless we manage switch everything that was mentioned in in one go. I guess it will depend on the time at which we get around to tackling this.
Comment 7 Thibault Saunier 2012-07-11 15:39:39 UTC
I started to work on the porting using gtkcompat here:

It is supposed to be a transitionnal state but I think this way we could start porting PiTiVi to GI and thus Gst-1.0 without making it completely incompatible with the current code we have.

There is obviuouly quite a lot of work to do still, and this branch was more about checking how possible it was for us to use the compatibility layer, I think the result is quite good, and we should follow on that branch.
Comment 8 Jean-François Fortin Tam 2012-09-02 04:18:02 UTC
Done with the 120+ commits between 2488645ecfd5c and 99d23dbf528d.