On Thu 25 Feb 2016 at 21:53:58 (+0100), Floris van Manen wrote: > > > On 25 Feb 2016, at 20:39, Jacques Menu Muzhic <[email protected]> wrote: > > > > > > Looks like you have an installation problem. > > > > Where did you install LP from? > > > i guess i found the source of the problem. > Many, but not all, of the scripts in the > /Applications/LilyPond.app/Contents/Resources/bin folder > have a first line defined as: > #!/usr/bin/env python
env presumably still exists on your system. Used thus, it allows shell scripts to look for the binary to run via the PATH rather than being hardwired in the script. Because you've presumably put a "python" pointing at python3 earlier in your PATH (to make it your default), this construction will find it, use it, and fall over. > When rewriting this to > #!/usr/bin/python > > The scripts will run as described in the online instructions That would indicate that, as far as the system is concerned, python is (a link to) python2. Good, your system (unless it's archlinux) probably isn't broken. You've only broken your part of it. If you work through other people's scripts changing #!/usr/bin/env python to #!/usr/bin/python you are storing up more and more problems in the future. If you really want to stick with a PATH default of python3, then look at each script you feel the need to change. If it's written in python2, you can fairly safely changed the shebang to #!/usr/bin/env python2 which should run the correct version. The possible dangers if these are system scripts are that the file's timestamp is changed as are the contents. This could interfere with how their upgrade scripts function if they depend on these. Cheers, David. _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
