On 12 Sep 2001, Bernhard Herzog wrote:
> James Henstridge <[EMAIL PROTECTED]> writes:
>
> > The main changes are:
> > pango.Pango* -> pango.*
> > gtk.Gtk* -> gtk.*
> > gtk.Gdk* -> gtk.gdk.*
>
> Much better than the current naming scheme!
>
> The gtk.gdk.* looks a little strange, but I guess it comes from pygtk
> being a package.
Several people have commented on this. The reason for gtk.gdk is partly
to reduce namespace polution, and partly because the gtk.gdk module is not
independent of the gtk one. The gtk.gdk module is only created when
gtk._gtk is imported (the order of imports is all handled in
gtk.__init__). Having gdk at the toplevel would have made this a little
harder.
So far, all responses have been positive about this change. I won't make
the change yet in case there are people who haven't read their email yet
and are strongly opposed.
The Python 2.2 issue is a little less cut and dried. However, the python
2.2 type/class unification is the future. Also, whereas ExtensionClass
has needed some upgrades after almost every release of python, this code
will most likely be kept up to date :)
Once the class naming issue is resolved, I will look at doing a port to
python 2.2 on a branch.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
