Dario Lopez-Kästen wrote:
> From: "Leonardo Rochael Almeida" <[EMAIL PROTECTED]
>>Putting it in the Extesions directory, so that it can be imported by
>>external methods, doesn't seem to work, even if you put Extensions in
>>the PYTHONPATH, at least in my experience.
> hm... Putting it in the Extensions directory has worked for me using Zope
> 2.4.3 (I don't like to mess with the PYTHONPATHG in the Python Install)...
> Has this changed in later zopes?
What's wrong with twiddling PYTHONPATH?
My instance home has a 'Packages' directory, where I have stuff like
_ldapmodule.so (for ZLDAP), imaging.so, and the PIL and ldap packages.
My start script looks like this:
export INSTANCE_HOME PYTHONPATH
export STUPID_LOG_FILE STUPID_LOG_SEVERITY
echo `date` starting >> $INSTANCE_HOME/var/log/start_`date +%Y%m%d`.log
exec $INSTANCE_HOME/Python-$PYTHON_VER/bin/python2.1 \
-F $INSTANCE_HOME/var/FastCGI.soc -m 8099 -p - "$@" \
>> $INSTANCE_HOME/var/log/start_`date +%Y%m%d`.log 2>&1
All in all, it works pretty well. No need to sweat messing with
PYTHONPATH. All instance homes should do this, and have a Packages
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -