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