24 Feb
2009
24 Feb
'09
11:27 p.m.
Tres Seaver wrote:
Hanno Schlichting wrote:
I looked at this, but guessing or reliably getting to the zopepy script wasn't possible. So I added an explicit option to the script instead and documented it. You can now use:
bin/mkzopeinstance --python=bin/zopepy
on the SVN trunk. You can omit this option and it will use sys.executable as before.
Maybe we can detect buildout vs. tarball (e.g., the presence of 'buildout.cfg' vs. 'makefile'?)
What you have available inside the mkzopeinstance script is: sys.executable which is just your regular Python interpreter and then sys.argv which is ./bin/mkzopeinstance. As the 'zopepy' script can be called anything, I don't see how you can be smarter here. Hanno