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, 2008, at 1:45 PM, Larry Meyn wrote:
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 python uses it either. I removed PIL
from the site-packages and the program failed within a different
module. As I didn’t really have time to try and further diagnose
the problem, I decided do a Time Machine restore from immediately
before the 10.5.3 upgrade. This resolved the problem. I’m not
totally sure that 10.5.3 was the source of the problem and I realize
that I’m not providing enough detail for others to diagnose the
problem if 10.5.3 was the source, but I thought some people might
appreciate a heads up that upgrading to 10.5.3 might cause problems.
Larry
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
