Thomas Leonard wrote: >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 :-) > > The current situation is no different to the current situation with C programs trying to compile against gtk+.
Both gtk+ 1.2 and 2.0 use the same include file namespace (<gtk/*.h>), and the same function/type namespaces (gtk_* and Gtk*). If you want the compiler to correctly link a program, you need to tell it where the correct set of headers for the version of gtk+ is with a compiler flag. It is also possible to install the two different versions of pygtk in different location (currently by specifying a different prefix. I will probably add a configure argument to set the actual dir), and then setting PYTHONPATH to point at the desired version. James. -- Email: [EMAIL PROTECTED] | Linux.conf.au 2003 Call for Papers out WWW: http://www.daa.com.au/~james/ | http://conf.linux.org.au/cfp.html _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
