[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5536 musicxml2ly broken in all lilypond installers since 2.19.44

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Remaining python 2.4.5 compatibility issues have been fixed, please review. https://codereview.appspot.com/558920043

---

[issues:#5536] musicxml2ly broken in all lilypond installers since 2.19.44

Status: Started
Created: Wed Jul 17, 2019 08:19 AM UTC by Knut Petersen
Last Updated: Sun Jul 21, 2019 05:31 PM UTC
Owner: Knut Petersen

In lilypond 2.19.44 an enhanced but broken version of musicxml2ly was shipped. Every lilypond installation that was made using one of our official installers since lilypond 2.19.44 contains an unusuable musicxml2ly script.

An example: Instead of producing

 \clef "treble" \key c \major \time 4/4

musicxml2ly emits

  \clef "treble" \^@k^@e^@y^@ ^@c^@ ^@\^@m^@a^@j^@o^@r^@ \time 4/4

with the python 2.4.5 provided by all lilypond installers. (^@ here means an ASCII NUL byte)

The patch that introduced the problem was discussed in issue 4751.

After the patch was pushed Phil Holmes was the first to correctly realize that the enhanced musicxml2ly needs at least python 2.7, see https://sourceforge.net/p/testlilyissues/issues/4751/?page=1&limit=25#97dc

Although musicxml is used in GUB it is not affected because GUB uses the systems's python and not tools::python or linux-64::python as the interpreter for musicxml2ly.

---

Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

_______________________________________________
Testlilyissues-auto mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto