On Wed, 2003-09-03 at 00:46, James Henstridge wrote: > 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 .
Firstly, sincere congratulations on making the 2.0.0 releases. It is wonderful to see all your hard work over the years pay off so far. :) > 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. Agreed. > 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. Yes and yes. What do you think about moving the gtksourceview bindings into the main module (I'm not sure where exactly in the directory tree)? This is all said without having talked to the maintainer about his plans, but I like the idea of having a single-source download for this kind of stuff. Things like vte are different, since it includes the Python bindings in the main module. > I don't have many plans for pyorbit enhancements, other than removing > cruft needed to support older ORBit2 versions. > > Any comments? My only real request is to continue supporting Python 2.2. I was one of the people in favour of requiring 2.2 early on, so this risks sounding hypocritical, but the changes between 2.2 and 2.3 are not as large as from 2.1 to 2.2 and there will be a lot of installations with no plans to upgrade for some time. (OK, this is partly selfish: I've just got people at work beginning to use some apps in PyGTK and we have no upgrade plans in the near future for a large number of pragmatic reasons.) (In case that sounds wrong in email, I am not sure what your plans are -- this is just a pre-emptive $0.02 strike. :-) ) Cheers, Malcolm
signature.asc
Description: This is a digitally signed message part
_______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
