After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 744888 - The path of python is hard-coded as /usr/bin/python
The path of python is hard-coded as /usr/bin/python
Status: RESOLVED FIXED
Product: d-feet
Classification: Other
Component: general
0.3.x
Other FreeBSD
: Normal normal
: ---
Assigned To: D-Feet Maintainer(s)
D-Feet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-02-21 12:23 UTC by Ting-Wei Lan
Modified: 2015-10-17 17:31 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Use the path detected by autoconf instead of hard-coding /usr/bin/python (1.23 KB, patch)
2015-02-21 12:25 UTC, Ting-Wei Lan 		none Details | Review

Description Ting-Wei Lan 2015-02-21 12:23:34 UTC 
d-feet use #!/usr/bin/python, which doesn't work on systems that have python installed in different locations.
Comment 1 Ting-Wei Lan 2015-02-21 12:25:48 UTC 
Created attachment 297492 [details] [review]
Use the path detected by autoconf instead of hard-coding /usr/bin/python
Comment 2 Michael Biebl 2015-10-07 18:21:37 UTC 
I'm not sure if using @PYTHON@ is the right idea/choice.

Reading [1], 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.




[1] https://www.gnu.org/software/automake/manual/html_node/Python.html
Comment 3 Ting-Wei Lan 2015-10-17 17:31:38 UTC 
@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?