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

2008-06-02 Thread 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

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

2008-06-02 Thread Christopher Barker
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

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

2008-05-30 Thread Larry Meyn
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. Larry On May 29, 20

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

2008-05-29 Thread Larry Meyn
I¹ve been successfully using parallel python with a framework build of python 2.5.2 on an 8-core Mac Pro. After upgrading to OS X 10.5.3 yesterday my program quit working and the traceback indicated that it failed within PIL. However, my code does not import PIL and I don¹t believe that parallel