|
From: | Jonas Hahnfeld |
Subject: | Re: Python 3 |
Date: | Sat, 21 Sep 2019 14:01:13 +0200 |
User-agent: | Evolution 3.34.0 |
Am Samstag, den 21.09.2019, 13:43 +0200 schrieb Werner LEMBERG: > >> Well, I prefer a series of patches instead of a single patch. > > > > > > Ok, I'll split the third one. My concern was that a single part of > > > the series won't bring any benefit on its own. So for example only > > > changing the division operator will not make musicxml2ly work with > > > Python 3. > > > In case there are patches within a series of patches that don't > compile, please say that in the commit message for the benefit of `git > bisect'. I think it is better to have smaller, easily comprehensible > but probably uncompilable changes than a single, working chunk that is > hard to read. All patches in the progress of porting to Python 3 won't fully work until all remaining issues are fixed. That said, I've split the third patch ("Fix musicxml2ly with Python 3") into four smaller logical groups. I don't really mind which version is applied, the outcome is the same. Regards, Jonas
0001-musicxml-Replace-new.classobj-by-type-for-Python-3.patch
Description: Text Data
0002-musicxml2ly-Fix-calls-to-functions-from-string.patch
Description: Text Data
0003-musicxml2ly-Fix-handling-of-encoded-data.patch
Description: Text Data
0004-musicxml2ly-Fix-integer-calculations-for-Python-3.patch
Description: Text Data
signature.asc
Description: This is a digitally signed message part
[Prev in Thread] | Current Thread | [Next in Thread] |