Sidnei da Silva wrote:
Looks like INSTANCE_HOME/lib/python is added to PYTHONPATH at some
point during startup, but not on the zopectl/runzope scripts.
I've tried installing eggs into INSTANCE_HOME/lib/python and they
won't load unless it's added to PYTHONPATH at startup time.
Thus, I propose to add INSTANCE_HOME/lib/python to PYTHONPATH on the
said scripts. Anyone against making this change all the way down to
Zope 2.9?
we've also seen a need to add an arbitrary path to PYTHONPATH in these
script for situations like using ian bickings workingenv. workingenv
constrains the execution and installation environment to an arbitrary
directory(no more installing eggs into the site-packages).
Might be nice to have this as an option for mkinstance; maybe --home to
make it similar to disutils?
-w
begin:vcard
fn:david morriss
n:morriss;david
org:The Open Planning Project
email;internet:[EMAIL PROTECTED]
title:Senior Engineer
url:http://www.openplans.org
version:2.1
end:vcard
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
