Re: Distributions upgrading to Python 3

[Graham Percival]

On Mon, Oct 18, 2010 at 11:57 PM, Matthias Kilian
<address@hidden> wrote:
> (unlurking, i didn't spend much time on lilypond recently)
>
>> 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.
>
> But are those scripts supposed to be used without runnig autogen.sh
> (and implied configure) first?

Anything that's used to build the website (as opposed to the html
version of the docs) cannot rely on configure.  This affects
scripts/build/ create-*.py website_post.py bib2texi.py

... admittedly, those are getting called with
    python scripts/build/foo.py
, probably precisely to avoid this problem.  So I guess that's not a concern.

I was incorrect in a previous email -- it's stuff in scripts/auxiliar/
that I run manually, not stuff in scripts/build/.  scripts/auxiliar/
makelsr.py node-menify.py strip-whitespace.py


>> > Would it be feasible to use "#!/usr/bin/env @PYTHON@" or
>> > "#!/usr/bin/env @TARGET_PYTHON@" for all Python scripts, using the
>> > basename of the appropriate Python executable in place of the Make
>> > variables?
>
> #!/usr/bin/env YOUR_FAVORITE_INTERPRETER
>
> should not be used ever. At least not for scripts that will be
> installed system-wide.

Why not?  IIRC, we had to add this to work around some problem in OSX.
 The discussion is in the email archives... hopefully somebody can dig
it out for us.

If there's a good reason not to do this, and a better way of solving
whatever problem we solved with /usr/bin/env python, I welcome a
change.

Cheers,
- Graham