[Pythonmac-SIG] bundlebuilder --standalone not working

[Jack Jansen]

On 24-sep-03, at 16:23, Bob Swerdlow wrote:

> I finally figured this out.
>
> Our application launches background scripts using Popen2, and we were 
> just
> specifying "python" as the command, passing it the script name from our
> bundle.  Of course, this would cause the default python to run rather 
> than
> the one in our standalone package.  By specifying the full path in the
> command, it finds a compatible python and these problems are avoided.

This is what Python has sys.executable for: it is the path to the 
current
interpreter. And the bundlebuilder design has gone through quite some
pains to make sure it actually points to a valid interpreter...
--
Jack Jansen, <Jack.Jansen at cwi.nl>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma 
Goldman