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
I still think coot is somehow using /usr/bin/python, despite the fact
that configure fails unless I specify -I/sw/include/python2.5, or at
least it is using the OS X system's python filesystem to create its
own sys.path
If I explicitly export into PYTHONPATH everything that gets coded in
