rbrewer wrote: > > I recently upgraded our Plone 3.0.5 site to Plone 4.0.2, running on Mac OS > X Server 10.6 (using the Mac OS X binary installer, not the Unified > installer), and I am running into a problem. >
This is not always necessary related to Plone itself, but might be a mess with OSX system Python installation. Try this 1) Check what Python interpreter is used by opening bin/instance or similar file and read its first line (like #!/usr/bin/python2.6) 2) Start this Python interpreter in verbose mode python -v 3) Type in command import _imaging 4) Import tracing dump should be printed in to the terminal 5) Inspect the dump and see the actual .so files Python tries to read 6) If you still cannot figure out what's going on please paste the related import traces to this mailing list thread It might be that e.g. OSX update 32 bit -> 64 bit might have left around bad .so files. If nothing helps then create new Python installation using virtualenv utility and install fresh PIL installation there. ----- Mikko Ohtamaa Mobilize your Plone site - http://webandmobile.mfabrik.com mFabrik - Freedom Delivered. - http://mfabrik.com -- View this message in context: http://plone.293351.n2.nabble.com/imaging-so-not-found-tp5887646p5891283.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
