I have just branched pygtk, pyorbit and gnome-python in CVS. If you want to get the 2.0 branches, you will need to switch your branches over to the branches:

   cd pygtk; cvs update -r pygtk-2-0 .
   cd pyorbit; cvs update -r pyorbit-2-0 .
   cd gnome-python; cvs update -r gnome-python-2-0 .

Development on the HEAD branch of pygtk will look at adding support for new GTK 2.2 APIs. It shouldn't take anywhere near as long to get the 2.2.0 release ready. If no one complains, I would also like to remove the GtkGLArea bindings from PyGTK. Since GtkGLExt seems to have an active maintainer and Python bindings, there doesn't seem to be too much need for it. If it is needed, the binding could easily be moved to GtkGLArea itself.

For gnome-python, it probably makes sense to focus on Gnome 2.4 as it is very close to release, since it includes a number of improvements relevant to the Python bindings. Among other things, it probably makes sense to kill the gnome.zvt binding.

I don't have many plans for pyorbit enhancements, other than removing cruft needed to support older ORBit2 versions.

Any comments?

James.

--
Email: [EMAIL PROTECTED]
WWW:   http://www.daa.com.au/~james/



_______________________________________________
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/

Reply via email to