On Jan 30, 2009, at 10:50 AM, Nathaniel Echols wrote:
the binaries I was using of coot-0.5-pre1
had this problem, while coot-0.5.1-pre1-1661 used the correct
interpreter.
That sounds like something I made, in which case I am even more puzzled.
The interpreter is actually supposed to be coot itself - I don't think
/sw/bin/python is going to do you any good, since it doesn't have
access to
the memory of the running coot process.
OK, but somewhere coot is making the decision to use the system's
python libraries in sys.path, so I am assuming it can only get these
from /usr/bin/python.
I think if I can consistently get it to use /sw/bin/python, then at
least I will know what I am trying to fix.
