On Sun, Oct 17, 2010 at 5:59 PM, Graham Percival <gra...@percival-music.ca> wrote: > On Sun, Oct 17, 2010 at 05:38:20PM -0700, Patrick McCarty wrote: >> --) Two scripts still have "/usr/bin/python" lines >> (python/auxiliar/manuals_definitions.py, and scripts/build/pytt.py). >> Those should be changed to "@PYTHON@", right? > > python/ yes, since it's not something that people call manually. > But stuff in scripts/build/ shouldn't have @PYTHON@, otherwise > it'll bork if you call it manually.
Um, I should have phrased my question differently: Most python scripts in python/ and scripts/ use @PYTHON@, @TARGET_PYTHON@, or "/usr/bin/env python". There are two exceptions, one in python/ and one in scripts/, that use a fixed path to the executable (/usr/bin/python). If you do a "git grep", you'll see what I mean. Are these two scripts special, or should they be changed to use @PYTHON@ ? Thanks, Patrick _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
