On Fri, 20 Aug 1999, Jeff Bauer wrote:
Andreas Kostyrka wrote:
Basically, I've got here a standard RH6.0 linux system, and being nice, I this time decided to let the standard 1.5.1 python be, and compiled my own 1.5.2 in a seperate path.
Does your pcgi info file (Zope.cgi) specify a PCGI_EXE directive that points to your new python 1.5.2 path? Yes it does: #!/opt/mtg/Z/ZOPE-2.0.0b4/pcgi/pcgi-wrapper PCGI_NAME=Zope PCGI_MODULE_PATH=/opt/mtg/Z/ZOPE-2.0.0b4/lib/python/Zope PCGI_PUBLISHER=/opt/mtg/Z/ZOPE-2.0.0b4/pcgi/pcgi_publisher.py PCGI_EXE=/opt/mtg/bin/python PCGI_SOCKET_FILE=/misc/home/mtg/mtgzope/var/pcgi.soc PCGI_PID_FILE=/misc/home/mtg/mtgzope/var/pcgi.pid PCGI_ERROR_LOG=/misc/home/mtg/mtgzope/var/pcgi.log PCGI_DISPLAY_ERRORS=1 BOBO_REALM=Zope BOBO_DEBUG_MODE=1 STUPID_LOG_FILE=/tmp/debug.log INSTANCE_HOME=/misc/home/mtg/mtgzope SOFTWARE_HOME=/opt/mtg/Z/ZOPE-2.0.0b4/lib/python
The problem is cleanly visible in the sourcecode: /*pseudo python translation*/ exec(PCGI_EXE,string.split(PCGI_EXE,"/")[-1],...) If this makes sense is questionable, and it's an bug if the python in PCGI_EXE is not the first python on PATH. Andreas -- Andreas Kostyrka | andreas@mtg.co.at phone: +43/1/7070750 | phone: +43/676/4091256 MTG Handelsges.m.b.H. | fax: +43/1/7065299 Raiffeisenstr. 16/9 | 2320 Zwoelfaxing AUSTRIA