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

[Robert Park <rbpark exolucere ca>]

On Thu, Oct 28, 2010 at 1:58 AM, Tomeu Vizoso <tomeu tomeuvizoso net> wrote:
> On Thu, Oct 28, 2010 at 02:29, Robert Park <rbpark exolucere ca> wrote:
>> And in fact, if I remove the 'import pygtk' and 'pygtk.require' from
>> my program, it continutes to operate totally normally.
>>
>> Can somebody clarify the meaning of the pygtk import statement and
>> whether or not it is still relevant while using the
>> gobject-introspection bindings?
>
> If anybody is able to clarify that, please update
> https://bugzilla.gnome.org/show_bug.cgi?id=621525 .
>
> I'm not sure what can be done without screwing current users.

Well, obviously people who have not yet ported to the introspection
bindings would continue to use "import pygtk" and continue to use
pygtk without "getting screwed".

But, in my limited understanding (as a developer of applications who
_uses_ bindings but not a _developer_ of bindings), it seems to me
that "import pygtk" is completely irrelevant and obsoleted by the
introspection bindings. It seems to me that it can be safely dropped
from the program without impacting the operation of the program at
all. Am I wrong? Is there something subtle it does that I'm not aware
of? What does it do?

By the look of that bug, it seemed to be relevant at some point in
time back when pygi was only for gtk, but now that pygi/pygobject have
been merged and cover the whole range of introspection stuffs, it just
seems to be irrelevant.

(if it matters, I'm using the stock ubuntu maverick packages for
everything. is it possible that ubuntu has packaged this in such a way
that gi is in the pythonpath by default, but non-ubuntu users will
require the 'pygtk.require' stuff in order for it to work?)

-- 
http://exolucere.ca