> 2008/5/30 Farshid Lashkari <fla...@gmail.com>:sys.executable typically means the "current" executable, and py2exe etc
> > I'm not sure if there will be any side affects to modifying
> > sys.executable though. Should this be the official way of supporting
> > embedded interpreters or should there be a
> > multiprocessing.setExecutable() method?
> +1 for setExecutable (I'd prefer set_executable, to be PEP 8
already fiddles with that. The question in such a context seems to be "what
executable should I use for this processing functionality?". In a py2exe
like environment, it might not be unreasonable to assume that if a custom
executable is to be used, that custom executable may have a different
command-line or other special requirements. Further, I could imagine a
system that uses an alternative way of starting processes (eg, 'distributed
COM') where the concept of 'executable' (or even 'command-line') don't make
So it seems that maybe simply "setExecutable()" isn't the correct
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.