On Tue, Jan 21, 2003 at 09:43:06AM -0200, Christian Reis wrote:
> On Tue, Jan 21, 2003 at 11:06:49AM +0000, Thomas Leonard wrote:
> > Actually, it might be a PyGTK problem. Looks like the infamous
> > ref-counting bug ("this object is only referenced by signal handlers, so
> > I'm going to wipe __dict__"):
>
> Well, at least not an installation problem ;) but I concede.
Hmm, actually it *was* my problem. I'm so used to empty __dict__'s being
pygtk bugs, but this one really was an uninitialised object ;-)
[...]
> > Doesn't pygtk.py search sys.path? In that case, it should still find stuff
> > in /usr/local, even if python is in /usr (provided /usr/local is in the
> > default search path). I think there's a problem if you've installed some
>
> But for Python installed by default with prefix /usr, /usr/local is
> not in sys.path, is never searched, and it won't work.
Ah, I guess this is a Debian thing, then. I've added a note to our list of
pygtk hints.
Thanks,
--
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/
