Jim, I am sure you are right, but I am not of a mind to reinstall my whole system right now for the sake of making thumbnails.. :( Maybe in two months, when I have a little break in my (very busy) work schedule.. So, is there any way I can install PIL into the working Zope (binary) install, or use symbolic links to make Zope see the deb-installed PIL? (my working zope install was installed from the Linux binary, non-deb, that was available from zope.org) Thank you, Chris Jim Penny wrote:
On Thu, Apr 12, 2001 at 02:26:46PM -0700, Chris Beaumont wrote:
Hello,
I'm sorry to ask such a dumbish newbie question..
I am using the Zope binary release on a Debian Linux system. Debian of course comes with its own Python, so now there are two Pythons on my server box. I recently installed PIL from a .deb, and now I am finding that my Zope installation can't see it.
Don't. Install from source or use the debian binary.
The Linux binary package from zope.org is a bletcherous mistake. it enables new users (who normally have a perfectly good python installed) to get running more quickly, at the cost of being really confused on where to put things and how to install python extensions.
The source install takes all of 20 minutes, and is dead easy, i.e. unpack and make wo_pcgi
zope is apt-gettable in both sid (unstable) and woody (testing). while I personally do not like the FHS mandated locations the .deb uses, they are quite in line with all other debian packages.
Jim
(I assume because my Zope's Python needs to be told where to look for it)
What is the proper way (or configuration files I need to edit/link I need to create, etc?) to rectify this situation?
Thank you!
Also.. another related question.. is there any way the PIL could be available to both Pythons without a conflict, or having to install it again..
Thanks.. Chris