Quoting James Henstridge <[EMAIL PROTECTED]>:
> I have been wondering if it is worth stabilising the extension class
> branch and releasing it as a new version for use with gtk-1.2 (which
> would
> also mean converting over the rest of gnome-python), or go straight on
> to
> port to gtk-1.3/4. Does anyone have any comments on this?
IMHO, you should do it in two steps: Releasing a new version before
gtk-1.4 will help to find bugs which are not in gtk (because gtk
is stable then). Later, when pygtk is stable, you can adjust it for
(the unstable) gtk-1.4. This way, you will have less sources of
bugs and problems.
> Another thing I have been thinking about for the gnome-2.0 release
> (whenever that happens) is whether it would be a good idea to not
> include
> pygtk as part of the gnome-python package (so it would have to be
> installed separately). Does this sound like a good idea?
I, for example, cannot use gnome but I use pygtk. Therefore,
I depend on an independend pygtk package (a .tar.gz to be precise).
The reason for this is: I'm developing in a tight/secure environment
and I must restrict myself to the smallest set of tools possible.
--
==============================================
Sowatec AG, CH-8330 Pf�ffikon (ZH)
Witzbergstr. 7, http://www.sowatec.com
Tel: +41-(0)1-952 55 55
Fax: +41-(0)1-952 55 66
----------------------------------------------
Aaron "Optimizer" Digulla, [EMAIL PROTECTED]
==============================================
-------------------------------------------------
This mail sent through IMP: www.hepe.com
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
