On Jul 26, 2013, at 09:58 PM, Nick Coghlan wrote: >Not everybody uses generated script wrappers, though - if there is a >hardcoded "/usr/bin/env python" or "/usr/bin/python" in a shebang >line, the Python build tools won't touch it. There's also a whole lot >of software that isn't packaged at all - it's sitting around in user >and admin home directories, or maybe in a shared directory on a file >server or even in a private source control repo.
I actually think installing a script via setuptools should rewrite shebangs even in the case of /usr/bin/env. I love `#!/usr/bin/env python` *for development* but I really think its a bad thing to have for installed scripts. Certainly, for distro installed scripts, it's (usually) terrible. I think virtualenv installs are generally in the same boat though - if you're installing a script into a virtualenv, it's better to rewrite the shebang to use the executable that was used to install it. -Barry
signature.asc
Description: PGP signature
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
