Martin Aspeli wrote:
I don't have a usecase for executing the scripts with any python
interpeter other than the one which ran setuptools to generate them, and
therefore don't care for the hard-wired path manipulation
I would agree that having to mangle multiple scripts is annoying. On the
other hand, I find the activate/deactivate dance annoying. I rather
think that the scripts that buildout has created should not require any
special activation or introduction to a particular environment.
workingenv doesn't require that you activate before running scripts,
each script contains in effect what active/deactive does. Basically it
munges script creation to do:
#!/usr/bin/python -S
import sys, os
sys.path.insert(0, os.path.join(os.path.dirname(__file__),
'lib/python%s.%s' % (sys.version_info[0], sys.version_info[1]))
import site
virtual-python -- which might be the better/simpler solution, if you
just ignore the tree of symlinks -- selects the environment through the
interpreter itself (i.e., #!/path/to/virtual-python/bin/python).
Ian
_______________________________________________
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 )
