On 08.02.19 04:51, Carl Sorensen wrote:
On 2/6/19, 3:42 PM, "lilypond-devel on behalf of Knut Petersen" <lilypond-devel-bounces+c_sorensen=byu....@gnu.org on behalf of knut_peter...@t-online.de> wrote:>> - the need to make sure that `python` calls a python2 interpreter.> No idea how this could be solved elegantly. I guess it can't, so we > have again something to document... > Use /usr/bin/env python2? Does every python 2.x installation really contain a python2 executable?OSX 10.12 Sierra has python 2.7 but does not have a python2 executable. Only python.At least this is the case on my machine.
Gosh, didn't expect that. In that case, I'd vote for leaving python shebangs as they are.Arch is clearly not following (one of) the recommendation in the PEP, that python "should" deliver python2. So it's Arch's fault, and their (packagers/users') responsibility to take appropriate action.
Alex
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
