Two potential solutions: 1) Wrap the call to ltihooks.uinstall() with
try/except. 2) After the import, make a call that triggers the
exception since the plain "ltihooks" statement does not seem to be
enough.
First one seems like a good solution.
I committed it to PyGTK trunk.
Great, thanks.
I tried solution #1 and it worked, but I don't fully grok the
situation. For example, why doesn't the gtk\__init__.py run when I
start my extension directly from the command-line? Also why can't
ltihooks be located... I see it in the pygtk sources?
It's not installed, it's only used in 'uninstalled' mode, eg when running
pygtk from the source directory without installing it to a prefix such as
/usr/local. It's only useful on systems which uses libtool, I guess it's not
particularly relevant on Windows systems.
For my own knowledge... why would this problem only occur when my
extension is run from within mercurial (which is installed to the
python\Lib directory). When I test my extension by running it directly
in the source tree, it worked. In fact it seems like gtk\__init__.py
is not run at all in that case. Is that normal?
-Brad
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
