Bug 29424 - Migrate from PyGTK to PyGObject introspection-based bindings
Migrate from PyGTK to PyGObject introspection-based bindings
Status: NEW
Product: cairo
Classification: Unclassified
Component: general
1.10.3
Other All
: low minor
Assigned To: Carl Worth
cairo-bugs mailing list
https://bugzilla.gnome.org/show_bug.c...
:
Depends on: 40804
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-06 10:04 UTC by Andre Klapper
Modified: 2012-04-24 11:38 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andre Klapper 2010-08-06 10:04:37 UTC
./util/waterfall:import pygtk
./util/waterfall:pygtk.require('2.0')
./util/cairo-view:import pygtk
./util/cairo-view:pygtk.require('2.0')

Grep'ing for pygtk 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.