Is that dangerous?
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
I thought we had this before!? Although cannto find it quickly enough,
however..
a quick google says:
http://stackoverflow.com/questions/514371/whats-the-bad-magic-number-error
So, just remove ALL the pyc and let them recompile...
B
Is that dangerous?
If I move it I then get
ImportError:
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
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).
On Wed, May 04, 2011 at 01:16:29PM +0100, 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).
Yes, but you're deleting compiled python objects from _system_ directories,
and since normal users can't write to
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
I did delete the *.pyc files in the system directories, and they have now
reappeared
I've also edited the coot wrapper to remove the system directories as suggested
by Bill.
All seems to work now
thanks to everybody
Phil
On 4 May 2011, at 15:29, Ben Eisenbraun wrote:
On Wed, May 04, 2011
I'm hosting nightly builds now, and none of the more recent versions should
have this in the wrapper script. Please let me know if somehow that isn't the
case.
Bill
On May 4, 2011, at 9:10 AM, Phil Evans wrote:
I did delete the *.pyc files in the system directories, and they have now
