Dear Phil, Paul, Ben, Bernhard et al: Sorry to arrive 8 hours late to the party, but first my apologies to Phil. I thought I had fixed this problem by excising from the coot wrapper script the path in /System/Library, i.e.,
export PYTHONPATH=/Library/Coot/lib/python2.7/site-packages:/Library/Coot/lib/python2.7/site-packages/gtk-2.0:/Library/Coot/share/coot/python:$PYTHONPATH So my guess is you have $PYTHONPATH or else my fix somehow doesn't work. The reason this is problematic is ultimately because coot is using python 2.7 libraries (included). (Old whine, new bottle.) Anyway, it would be good to find which is the source of the problem. I think I need to add to PYTHONPATH to keep phenix happy, but if the user has set $PYTHONPATH, then what is in the wrapper script becomes fragile. Any feedback will help me make this better. Thanks. Bill On May 4, 2011, at 5:33 AM, Phil Evans wrote: > OK that worked thanks > > I'm not sure whether these files got copied over from my old machine - I > didn't do the copy myslef > > Phil > > On 4 May 2011, at 13:16, Paul Emsley wrote: > >> On 04/05/11 13:11, Phil Evans wrote: >>> Is that dangerous? >> >> Not really, python makes the pyc files again (I understand). >> >>> If I move it I then get >>> >>> ImportError: Bad magic number in >>> /System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site.pyc >>> >>> after moving that I then get >>> >>> ImportError: Bad magic number in >>> /System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/os.pyc >>> >>> and so on I guess >> >> So I understand after a bit more googling. >> >> I should have recommended some sort of find: >> >> $ find >> /System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 -name >> "*.pyc" -delete
