Hello Knut, > Lukas thought of the following options > > 1) make musicxml2ly work again (by changing the Python version used, or by > fixing the problems with 2.4), or > 2) remove musicxml2ly from the distribution bundle, possibly > 2a) without replacement, > 2b) replaced by xml2ly > > My comments: > > Option 1: 'fixing' musicxml to be compatible with python 2.4 is a waste of > time. Updating python for all target platforms will take a lot of time. It's > not clear if someone volunteers to do the job. > Option 2a: not a real option, we need a working musicxml2ly (or > replacement) for 'bin/gub lilypond-test' and 'bin/gub lilypond-doc' > Option 2b: maybe that would work, but we still would see the need to update > python.
I’ve still got work on repeats handling finalization in xml2ly before it can be announced. The good news is that it’s pure C++11, no Python involved. JM _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel