On Wed, Jul 31, 2002 at 12:59:12PM -0700, Conrad Steenberg wrote:
> On Wed, 2002-07-31 at 12:45, Christian Reis wrote:
> > On Wed, Jul 31, 2002 at 08:53:11AM -0500, Jon Nelson wrote:
> > > On Mon, 29 Jul 2002 10:42:26 -0500
> > > Christopher Armstrong <[EMAIL PROTECTED]> wrote:
> > >
> > > > Why isn't the *official* PyGTK distribution using 'gtk2' as its
> > > > package name? This is going to make packaging *hell*. I implore
> > > > James to change it before PyGTK 2.0-final is released. (There's
> > > > always "import .. as ..")
> > >
> > > I agree. Please please please. That way, one doesn't have to do
> > > a whole-sale switchover! pygtk2-1.99.12 should be able to be
> > > installed alongside pygtk-1.6.8, without interference, if possible,
> > > just as gtk1.2.x and gtk2.x can be installed alongside each
> > > other without interference.
> >
> > Add me as a +1 to this idea, please.
> Hmmm, I just joined the mailing list to ask the same question ;-)
>
> Cheers!
For all those wondering why things are the way they are, please see bug
#70178:
http://bugzilla.gnome.org/show_bug.cgi?id=70178
James explains here why the official version cannot be allowed to coexist
with the current stable release. However, if packagers want, I could
package the whole of gnome-python (not just pygtk) with a different module
name, and people can just install that one instead.
If you want to write programs that will still work even if someone has
installed James' version instead, you can just start the main file with:
try:
import gtk2 as gtk
except:
import gtk
assert gtk.Window
Then do this in each submodule:
from __main__ import gtk
No problems :-)
--
Thomas Leonard http://rox.sourceforge.net
[EMAIL PROTECTED] [EMAIL PROTECTED]
GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
