> One request that has come up many times is to drop the "Gtk" prefix from
> the widget class names in pygtk.
>
> In the past, the answer has been that it would cause name space pollution
> for people doing "from gtk import *". However for the development series,
> using "from gtk import *" is discouraged more so than in the stable series
> (when the development branch goes stable, I intend to have all examples
> converted over to using "import gtk").
I consider `from gtk import *` to be evil (having myself suffered by
innocently using `from Tkinter import *`).
IMHO, `gtk.Button` is much better than either `GtkButton` or
`gtk.GtkButton`.
> As this would cause large source incompatibility, I am looking for
> people's opinions about such a change (I haven't decided which way I feel
> about this issue yet).
I guess it's either now or never.
> There is one other major change that I am considering (although it will
> affect the API far less) -- using the new python 2.2 features instead of
> ExtensionClass. I haven't started looking at how easy such a change would
> be (probably not that hard -- it would mainly be changes to the code
> generator and the gobject module).
Using 2.2 would be a good thing. OTOH, 2.2 isn't really here yet.
Personally, I'm in favor of switching as fast as possible. Yet, a
forced switch to 2.2 might make many people seriously unhappy
(including me).
--
Christian Tanzer [EMAIL PROTECTED]
Glasauergasse 32 Tel: +43 1 876 62 36
A-1130 Vienna, Austria Fax: +43 1 877 66 92
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
