Re: midi2ly

[David Wright]

On Thu 17 Jun 2021 at 14:20:52 (-0700), Kees van den Doel wrote:
> On windows 10, a fresh install of lilypond.
> On Windows "powershell"
> > midi2ly -V
> brings up a window "how do you want to open this file".
> On mintty (another CMD shell)
> mintty screen dump
> 
> bash: /cygdrive/d/Program Files (x86)/LilyPond/usr/bin/midi2ly:
> /usr/bin/python3: bad interpreter: No such file or directory
> 
> Can anyone tell me what's wrong?

Two possibilities strike me, not being a Windows user:

1) The first line of midi2ly is a shebang, ie
   #!/usr/bin/python3
   which is the recommended way to run Python 3 scripts.

Even where "python" alone now invokes python3 rather than
python2, python3 should still be defined.

2) The third line of midi2ly gives the script's name as
   # midi2ly.py -- LilyPond midi import script

The .py suffix should allow OSes like Windows to invoke
the appropriate interpreter. For help with this, perhaps
look at this post and this thread (both for convert-ly):

https://lists.gnu.org/archive/html/lilypond-user/2021-01/msg00140.html
https://lists.gnu.org/archive/html/lilypond-user/2021-05/msg00301.html

Cheers,
David.