Use /usr/local/bin/python if it exists and /usr/bin/python does not. If that also does not exist, try python from $PATH.
This allows check_lint.sh to work on FreeBSD without the need to manually specify PYTHON_EXECUTABLE.
Differential D9914
Support python in other than /usr/bin/python emaste on May 21 2015, 8:41 AM. Authored by
Details Use /usr/local/bin/python if it exists and /usr/bin/python does not. If that also does not exist, try python from $PATH. This allows check_lint.sh to work on FreeBSD without the need to manually specify PYTHON_EXECUTABLE.
Diff Detail Event Timeline
Comment Actions I'm happy to just switch to /usr/bin/env python in the scripts if everyone's happy with that (leaving the explicit PYTHON_EXECUTABLE override as it was).
Comment Actions That is to say, it seemed like this intentionally used /usr/bin/python if it exists, rather than relying on python in the user's path, and I tried to keep that behaviour. I'm happy with either of
|
You never set PYTHON_EXECUTABLE to /usr/bin/python, is it intentional, or you believe it would always be in PATH in this case?