[Pythonmac-SIG] Strange python behavior after upgrading to OS X 10.5.3

[Larry Meyn]

I was using a 2.5.2 framework build not the system python.  So the system
python shouldn't have been involved and the framework build wasn't changed
after the upgrade.  Another interesting quirk was that the new .pyc files
from my machine running OS 10.5.3 worked fine on my machine downgraded to OS
10.5.2.  I'll try to preserve the different .pyc files for future
investigation if I get some spare time, but "fix" of deleting the .pyc files
is simple enough for now.

--Larry


On 6/2/08 10:14 AM, "Christopher Barker" <Chris.Barker at noaa.gov> wrote:

> 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
> 
>