Subject: Re: [nmr_sparky] about sparky python script in fedora core 4 linux
From: Thomas Goddard
Date: Mar 28, 2006

Previous: 91

The trouble is that your Sparky and Chimera programs each include
their own Python but are using different Python versions. Sparky and
Chimera must use the Python version they were compiled against because
different Python versions are not binary compatible and both Sparky
and Chimera have C++ code compiled for the specific Python.

So the solution is to get the right Chimera version that will work
with your Sparky version. Here are details from the current release
candidate Sparky manual (linked on the Sparky page but a bit hard to find):

http://www.cgl.ucsf.edu/home/sparky/distrib-3.112/manual/extensions.html#Chimera

Only certain versions of Chimera will work with Sparky. For
Sparky 3.112 use Chimera version 1.2154 (known not to work with
Chimera version 1.2065 and earlier, nor with Chimera versions
1.2184 through 1.2199). For Sparky 3.110 or 3.111 use Chimera
version 1.2065 (known not to work with more recent Chimera
versions). For Sparky 3.106 use Chimera 1.1442. These restrictions
are primarily because both applications need to be using the same
version of Python. Sparky 3.112 uses Python 2.4, Sparky 3.111 uses
Python 2.3 and Sparky 3.106 uses Python 2.1. Sparky 3.110 does not
work with Chimera on the Mac as of March 2004 because Chimera on
the Mac requires a special version of Python.

The Sparky / Chimera interface is one of the only Sparky tools that has
a version matching problem (another is interface to AutoAssign program).

Tom