Hi citizens:
OS X comes with a version of python that doesn't play well with x-
windows-based modules, so when compiling and running coot, I would
like to make sure that I use a different version of python that has
things like the gtk2 modules in its sys.path. However, despite having
the
This has been a problem on and off with recent OS X binary builds too. 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. I don't know what the source of the
var
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 co
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
