Hi Ben and Pete - I did think about deleting (or moving) the .pyc files, but in
the newer of the two students' computers (3 weeks out of the box), there wasn't
a site.py file in that directory, only .pyc and .pyo, so I figured I'd better
not mess with it.
Thanks for the suggestions so far. I'll see if I can get the students back
here again and try editing the wrapper script.
Cheers,
Jared
On Mar 10, 2011, at 12:05 PM, Pete Meyer wrote:
> Ben Eisenbraun wrote:
>> Hi Pete,
>>
>>> Usually python will regenerate pyc files as needed (assuming the source
>>> files are available). So "find $COOTDIR -name "*.pyc" -exec rm {} \;"
>>> might be worth a try.
>>
>> This is true, but the import error is being generated by Coot trying to
>> read the _system_ .pyc files:
>
> Whoops - missed that.
>
>>
>>>> ImportError: Bad magic number in
>>>> /System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site.pyc
>>>> ImportError: Bad magic number in
>>>> /System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site.pyc
>>
>> And I would be hesitant to delete those. That said, in theory it really
>> shouldn't matter.
>>
>> -ben
>>
>> --
>> | Ben Eisenbraun
>> | SBGrid Consortium | http://sbgrid.org |
>> | Harvard Medical School | http://hms.harvard.edu |
------------------------------------------------------------
This email message, including any attachments, is for the sole use of the
intended recipient(s) and may contain information that is proprietary,
confidential, and exempt from disclosure under applicable law. Any unauthorized
review, use, disclosure, or distribution is prohibited. If you have received
this email in error please notify the sender by return email and delete the
original message. Please note, the recipient should check this email and any
attachments for the presence of viruses. The organization accepts no liability
for any damage caused by any virus transmitted by this email.
=================================
