Re: What is the significance of pygtk.require('2.0')?

[Robert Park <rbpark exolucere ca>]

Hi J5!

On Thu, Oct 28, 2010 at 4:15 PM, John Palmieri <johnp redhat com> wrote:
> We still have to support it because pygi will only be for Gtk 3.0 and so there will be a lot of legacy code running around.

This is news to me. I thought I was developing for Gtk2 with these GI
bindings. So Gtk2 will be dropped once Gtk3 is finalized?

> As for you needing to add them to new code, I don't think it is necessary though it may be on some systems.

Ok, so I can safely remove that from my program? It's only for legacy code?

>  In any case paths are important to keep consistent for legacy support since it is hard to know what will break if you move things around.  If we can emulate the old paths while moving the modules out then I say we do it.

Oh, I'm all for legacy support, but that's not really what I'm asking.
I don't personally care what path pygi is installed to. My question
is, what specific purpose does "pygtk.require('2.0')" serve when the
pygtk module is not ever referenced afterwards? Can I safely remove
this from my program without breaking anything?

>From my casual understanding, it seems to me that I'm importing the
old static bindings, telling them to require some version of something
or other, and then never using them in favor of using the
introspection bindings afterwards. I guess the root of the issue here
is that I am very confused about the meanings of the terms "pygtk",
"pygi", and "pygobject" and how they relate. I _thought_ that "pygtk"
meant "old, static bindings, crufty, unsupported, don't use anymore"
and "pygi/pygobject" meant "new, introspection, sexy, dynamic, the
future", so I'm just not sure why I am importing the pygtk module
_at_all_ when I am only using introspection bindings. What purpose
does "pygtk" module serve in introspection-land?

Thanks.

-- 
http://exolucere.ca