On *nix, the python executable that is installed in a Zope binary install is in the 'bin' directory. So you can execute it by specifying it explicitly by path.. (otherwise you might get the regular installed version of python) I found this helpful in getting the PIL installation on my Linux zope installation to work.. (it allowed me to run the setup.py scripts properly by including the Zope python in my path environmental variable and specifying the path to python and the python executable on the command line..) A similar situation probably exists for Windows.. Not having any experience at all running Zope under Windows, I wouldn't be able to help you much beyond that.. But you should be able to get somewhere with this info, it was very helpful to me and not documented anywhere.... -Chris Beaumont
Thank you Eric - Do you have any experience with Zope? As best I can tell as a relative Newbie to Python and Zope is that Zope only seems to execute in the context of the python installation it created at installation and so it doesn't seem to find resources such as PIL. I have no idea where that 'python path' is set or how to modify it except as the directory it is launched from. The issue is that Zope only sees the instance of Python that it installed itself. I tried clean installing Python first and Zope over it, forcing it to the same directory names, but the links to PIL still end up broken by this approach Any thoughts? Thanks again, Gary