Re: musicxml2ly produces unexpected EOF in .ly file

[Victor Rouanet]

Le 26/08/2018 à 12:56, Federico Bruni a écrit :
> Victor, please keep the list in Cc.

Sorry, newbie error :-)

> I was using lilypond packaged by Fedora, which uses python2 installed 
> on the system (currently 2.7.15).
> I've now installed 2.19.82 from lilypond.org, which uses the bundled 
> python .
> There's something wrong:
>
> $ file jafanosumu.ly
> jafanosumu.ly: data
>
> There's some bad encoding. See attached file.
>
> $ ls -lh ~/.local/lilypond/usr/bin/python*
> -rwxr-xr-x 2 fede fede 5,1K 24 giu 14.11 
> /home/fede/.local/lilypond/usr/bin/python
> -rwxr-xr-x 2 fede fede 5,1K 24 giu 14.11 
> /home/fede/.local/lilypond/usr/bin/python2.4
>
> It's just my installation?

Same result for me. According to Phil Homes in the lilypond-user topic, 
the shlex module (used by musicxml2ly in utilities.py) didn't support 
unicode input prior to Python 2.7.3. That would explain why the 
conversion only fails with manually downloaded version of lilypond, 
which bundles python 2.4.5.
When I hand edit the musicxml2ly script, forcing it to use the system 
python version (2.7.13), the result file looks well encoded.

$ file -i jafanosumu_converted_using_python2.*
jafanosumu_converted_using_python2.4.5.ly: application/octet-stream; 
charset=binary
jafanosumu_converted_using_python2.7.13.ly: text/plain; charset=us-ascii