[Image-SIG] Re: PIL 1.1.4 and Python 2.3 on Mac OS X 10.3?
bob at redivi.com
Thu Nov 6 19:12:28 EST 2003
On Nov 6, 2003, at 6:57 PM, Bill Janssen wrote:
>> 2) the python executable is dynamically linked against the Python
>> by the system's runtime loader 
> This seems to be complicated further in the Mac case, due to something
> I don't understand fully called "frameworks", which seem to interact
> with the runtime linking in some fashion. Guess I'm going to have to
> learn about it just to make Python work. Sigh.
> Thanks for the nice summary, Fredrik!
The only way (that I can possibly think of) to cause this "Interpreter
not initialized" problem for a module you built yourself is if you have
more than one Python installed on your computer. The places to look
for them, unless for some reason you've set
DYLD_FALLBACK_FRAMEWORK_PATH yourself are:
Delete all the other ones and stick with what Apple gave you and your
problems should go away.
You should stop making this so hard on yourself.. besides, PIL is
available precompiled by way of Package Manager (albeit, missing
libjpeg and a few other things, but I will have a Panther version of my
Package Manager repository in a few days that will include a better
version of PIL).
More information about the Image-SIG