Note : If you write software...
If you write software, config files, makefiles, test cases, or any part of the software delivery ecosystem with hardwired paths to things embedded in them, you are officially a big bozo. Not the fun kind with a red nose and big shoes either. The only hardwired path that's OK is /bin/sh on a shebang line. But if you do things like this:
Thu Dec 28 09:24:55 2017 - permalink -
You should be sent to work 1st level phone support on the midnight shift in Somalia until you learn better. Grrrrrr.
This is the right way to do this is:
env can reliably be found there and it will "discover" where python happens to actually be installed on that machine, so long as it is in $PATH somewhere. Similarly, learn to use constructs like:
In short, NEVER make assumptions where things are. Always discover it at configuration time.