[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What is holding up 2.20 release?

From: Jonas Hahnfeld
Subject: Re: What is holding up 2.20 release?
Date: Tue, 17 Dec 2019 22:03:19 +0100
User-agent: Evolution 3.34.2

Answering to myself:

Am Dienstag, den 17.12.2019, 19:58 +0100 schrieb Jonas Hahnfeld:
> Am Samstag, den 16.11.2019, 21:52 +0100 schrieb David Kastrup:
> > a77f387207 Fix / Python 2.4.5 incompatibility
> I think it would be good to take this, but it requires
> 78225bc1b3 Chord names clean-up; no more Banter, exceptionsPartial or 
> \powerChords.
> because the \powerChords chordkind has a format in the middle (see
> changes in ChordNameEvent).

There's actually an equivalent fix for ChordNameEvent by using the
modulo operator. With the two patches attached, stable/2.20 is passing
a full check with Python 2.4.6 on my system (the first one is actually
the original commit a77f387207 without the changes for ChordNameEvent).

Hope this helps,

Description: Text Data

Attachment: 0002-Second-fix-for-musicxml2ly-with-Python-2.4.patch
Description: Text Data

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]