Hi everybody,
For more than 10 years gub/specs/lilypond.py used /usr/bin/python.
That means that during lilypond-test the system's python interpreter
is used as the interpreter for the musicxml2ly script, not our own
python in target/tools. At some currently unknown point in time
musicxml2ly became incompatible to our python 2.4. The hidden usage of
the system's python masked that incompatibility.
With our python 2.4 musicxml2ly does not barf, it simply produces
garbage that lateron causes lilypond to fail.
@Werner: Didn't you write something about updating python in gub?
I assume you're referring to the situation that (e.g.) 2.19.82's
musicxml2ly chokes with an error message regarding UTF-8 and producing
ly files containing garbage bytes in each literal string.
On my system, your description matches: Current Master's musicxml2ly
python script runs fine using my local python2 (2.7.15rc1) but has the
error using 2.19.82's python2.4 (2.4.5).
--------------------------------------------------------------------------------------------------
5e44fec38f33997109bc85c099472b2736649fde is the first bad commit
commit 5e44fec38f33997109bc85c099472b2736649fde
Author: Frederic Gohier <fgohie...@hotmail.com>
Date: Thu May 10 11:12:44 2018 +0100
Fix crash when using musicxml2ly
Issue 5317
Crash when running musicxml2ly
:040000 040000 32b11d27366ff7d629f2b6ca4d250a08293d6ece
750f9ccdbec7fa68babf3f4414aecb70f57c812b M python
--------------------------------------------------------------------------------------------------
So this might be the "currently unknown point in time"?
Best
Lukas
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
