GNOME Bugzilla – Bug 744888
The path of python is hard-coded as /usr/bin/python
Last modified: 2015-10-17 17:31:38 UTC
d-feet use #!/usr/bin/python, which doesn't work on systems that have python installed in different locations.
Created attachment 297492 [details] [review]
Use the path detected by autoconf instead of hard-coding /usr/bin/python
I'm not sure if using @PYTHON@ is the right idea/choice.
Reading , it says: "The name of the Python executable"
This means, it's not necessarily set to the full path, but rather python3, python2.7 etc.
@PYTHON@ can be wrong if users manually set it, but I don't find an alternative that we can use in automake. Should we just try to find it in PATH if PYTHON is not a full path?