Larry Meyn wrote:
I had the same problem on another Mac just upgraded to 10.5.3 from 10.5.2. This time the traceback was a little more helpful and the error occurred after opening a .pyc file. The solution was to delete all the .pyc files used and the newly regenerated ones worked fine.
Does this mean that Apple upgraded Python? That would be a first, and a good sign.
However, an upgrade to python within the 2.5 series shouldn't break *.pyc files, so I wonder what's up. Did they go 64 bit with the interpreter?
-Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [EMAIL PROTECTED] _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
