On Fri, Aug 02, 2002 at 02:54:54PM -0300, Christian Reis wrote: > On Fri, Aug 02, 2002 at 05:35:52PM +0100, Thomas Leonard wrote: > > Whatever the mechanics of it, and whatever analogy you choose, the effect > > from a user or developer's POV is: > > > > - Gtk2 doesn't break things. > > - Pygtk2 does. > > It's true at least for users (for developers, the installation of GTK+ > does change things somewhat).
Does it? I was still able to compile all my old 1.2 programs just fine after installing Gtk+-2.0. The header files all go in a different directory and pkg-config uses the name 'gtk+-2.0' instead of 'gtk+', so there shouldn't be any problems at all. > The thing with C APIs is that you can tie your application to a certain > version of the library, and since you have separate include/linkage > processing, it ends up working fine for linkage, which is what users > really need. I think it works for both users and developers. > Since Python only offers one of these mechanisms, we're left in the cold > when libraries/modules are updated, and that's where namespace > separation comes into play. Maybe Guido has an opinion on this? :) Which is why you can create modules with different names. You could even create a source file called 'gtk.py' that just does 'from gtk2 import *' and then everywhere else in your program do 'import gtk'. Noone seems to have explained what problems renaming the module causes (especially since this is what my version does, apparently without any difficulties). What difficulties can users and/or developers expect to face using my version, due to the '2' in the name? -- 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/
