Python scripts use hardcoded #!/usr/bin/python instead of #!/usr/bin/env python - Redmine #2401
The hardcoding of /usr/bin/python makes it overly difficult to point the
build to another python installation.
There is also one script, scripts/make_gromos_rtpy, that has
#!/usr/freeware/bin/python
Would be nice to have that fixed. Will also make it easier to migrate to using Python3.
(from redmine: issue id 2401, created on 2018-02-06 by akesandgren, closed on 2018-03-06)
- Relations:
- relates #1786 (closed)
- Changesets:
- Revision e6174dd4 by Mark Abraham on 2018-02-08T21:52:36Z:
Use more portable python shebangs
Per https://www.python.org/dev/peps/pep-0394/#recommendation, we
should use env, and point it at python2. When we either make them 2/3
or just-3 compatible, this should change.
Some distros (notable Arch Linux) already point python at python3 so
we should choose to be explicit, and thus somewhat portable.
Fixes #2401
Change-Id: Icf98e04660c798d10b167f971b20698e0741994a