Thanks for the input so far!! OK, I've made a little progress. By comparing the Python tree in Zope and the Python tree in ActiveState I guessed that putting the packages in "C:\PROGRA~1\WebSite\bin\lib" would work. More specifically, I put the sping and PIL directories in that path and not in a sub-directory called "site-packages". This allows me to import sping just fine. When I try to import PIL (indirectly through sping) I get an error that it can't find the _imaging C libraries. The _imaging.pyd file is in the DLLs directory in ActiveState and it works fine there. I have tried many, many locations in the Zope installation (even in the system32 directory) and can't seem to find one that works. Does anybody have an idea about this one? Thanks -----Original Message----- From: Chris Withers [mailto:chrisw@nipltd.com] Sent: Tuesday, September 17, 2002 9:09 AM To: Friedlander Paul Cc: 'Dieter Maurer'; 'zope@zope.org' Subject: Re: [Zope] I can't seem to get site-packages to work under Win32 Friedlander Paul wrote:
Thanks for the feedback.
The debug screen shows "C:\PROGRA~1\WebSite\bin\lib\site-packages" under syspath and "C:\PROGRA~1\WebSite\lib\python" for SOFTWARE_HOME.
I have tried putting a site-packages directory in the following locations with no luck.
C:\PROGRA~1\WebSite\bin\lib\site-packages C:\PROGRA~1\WebSite\lib\python\site-packages
Any other ideas?
You could try putting your site-packages dierctory in the PYTHONPATH: set PYTHONPATH=C:\PROGRA~1\WebSite\bin\lib\site-packages cheers, Chris