Dow_Hurst wrote: > After perusing the archives for explanations of Modeller and Python > interactions, it isn't apparent to me that Modeller couldn't use a > later interpreter and modules if the paths are set correctly.
The Python interpreter is built into the executable, so you cannot use a different one. You can, however, use other *modules*, as long as they are compatible with the Python 2.3 interpreter. This generally means that earlier pure Python (.py) modules will work, or later .py modules that do not require any 2.4 features will also work. What will generally _not_ work, however, are any modules which have a binary component (i.e. .pyd, .dll, or .so files) as these generally require a specific Python interpreter version.
> I understand that Modeller can be made aware of standard python 2.3 > modules with the PYTHONHOME variable. However, I haven't found a > clear yes or no on using a Python 2.4 standard installation with > Modeller. Is it possible to disable the internal Python 2.3 > interpreter linked into Modeller and force Modeller to use a system's > Python 2.4 installation?
> If not, then I could just compile/install > Python 2.3. I use SUSE 9.3 and 10.0 mainly at the moment in our lab > at UNCG on all the machines so I don't have a native install of the > older Python. Uninstalling Python 2.4 breaks several packages so a > side by side compile/install is probably easiest.
I certainly recommend this approach: http://salilab.org/modeller/8v2/manual/node10.html Compiling Python 2.3 from source is fairly straightforward on a modern Linux system, and you can install in /usr/local or some other location which won't conflict with the existing 2.4 install.
The next release of Modeller will be available as a 'true' Python module, so will be interoperable with any sufficiently recent Python interpreter.
Ben Webb, Modeller Caretaker