cp.recipe.cmd may be helpful

Mark Visser wrote:

I'm using buildout for managing a project that runs on several different python interpreters, some of which are embedded in other applications. As such, I'm at the whim of those packaging python for those applications, and sometimes they don't set things up... well, optimally.

The problem I've run into is that one of the exposed non-standard python interpreters (mayapy) is actually a shell script. Thus, you can't use its direct path with a shebang. Normally, I get around this by using #!/usr/bin/env mayapy.

For the life of me, I can't figure out a way to pass this to buildout. I've tried this:

[mayapy] executable = /usr/bin/env mayapy

[mayatests] python = mayapy ... etc

But buildout doesn't like the space. Is there a way to specify executable options? I tried this to no avail:

[mayapy] executable = /usr/bin/env options = mayapy

Can anyone suggest a solution?

thanks, -Mark _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig