views:

30

answers:

0

I've a buildout.cfg to manage dependencies and create a bin/script, and then I can do an sdist and include the script in there. The problem I've got is that the script has #!/usr/bin/python2.6 instead of #!/usr/bin/env python. If I use a virtualenv then, it points to the virtualenv python runtime. I would be interested to be #!/usr/bin/env python as the app is 2.4 compatible as well. After lots of searching, it seems that buildout makes the scripts pointing to the python you are using. Not big deal, as I can always do an automatic replace while doing the sdist, but I was wondering if there's any option in buildout to change that. Best regards.