On Wed, 2004-03-10 at 07:21, Xavier Ordoquy wrote: > On Wed, 2004-03-10 at 01:27, Graham Ashton wrote: > > Failing that, if there's enough interest in getting pygtk included in > > the release set, what do people think of the second option? > > I see drawbacks (release deadline fixed,
Yes, that's an advantage for many people. Your users want to know that you will closely track the APIs that you are wrapping, and your developers need to know when they can help most effectively. And distros need to know when you will release new stable API so that they can depend on it in their scheduled releases. A release schedule makes sure that software gets released. This could clearly help gnome-python. > API coverage has to match the > gtk/gnome version You don't need to wrap 100% of the C API, but you should try. > with no further API addition) but I'm failing to see > the advantages. gnome-python gets released, publicised, distributed, and used. -- Murray Cumming www.murrayc.com [EMAIL PROTECTED] _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
