Am Samstag, den 21.09.2019, 12:09 +1000 schrieb Andrew Bernard:
> So let me get this straight.
>
> It's not the case that GUB is completely broken. We can still build
> releases.
>
> DK is working steadily to cherry pick items for 2.20.
>
> Python 2 to Python 3 is a major issue.
>
> So, I offe
>> So, I offered to do the 2->3 port a long time ago but circumstances
>> prevented me from doing so. Would it be constructive if I launched
>> into that aspect?
Yes, definitely.
> I've also started looking into this and used the branch
> dev/knupero/lilypy3devel as a starting point (see also
>
Andrew Bernard writes:
> So let me get this straight.
>
> It's not the case that GUB is completely broken. We can still build
> releases.
It's not broken _yet_ because Python 2 is still more or less available
and of course we can keep using it (ignoring security issues) as long as
we want. This
Jonas Hahnfeld via lilypond-devel writes:
> Am Samstag, den 21.09.2019, 12:09 +1000 schrieb Andrew Bernard:
>> So let me get this straight.
>>
>> It's not the case that GUB is completely broken. We can still build
>> releases.
>>
>> DK is working steadily to cherry pick items for 2.20.
>>
>>
Am Samstag, den 21.09.2019, 11:20 +0200 schrieb Werner LEMBERG:
> >> So, I offered to do the 2->3 port a long time ago but circumstances
>
> >> prevented me from doing so. Would it be constructive if I launched
>
> >> into that aspect?
>
>
> Yes, definitely.
>
> > I've also started looking int
Am Samstag, den 21.09.2019, 11:25 +0200 schrieb David Kastrup:
> Jonas Hahnfeld via lilypond-devel <
> lilypond-devel@gnu.org
> > writes:
>
> > Am Samstag, den 21.09.2019, 12:09 +1000 schrieb Andrew Bernard:
> > > So let me get this straight.
> > >
> > > It's not the case that GUB is completely b
Jonas Hahnfeld writes:
> Am Samstag, den 21.09.2019, 11:25 +0200 schrieb David Kastrup:
>
>> I haven't checked yet, but at the current point of time, the best
>> patches will be those running under both Python 2 and Python 3 without
>> having to special-case code. Those can be applied to master
> If I remember correctly, this will be the time that we definitely
> have to retire the PowerPC MacOSX version (it's not clear anybody is
> actually using it, though).
Hmm. Looking into MacPorts, I don't see any restriction for using
python 3.7 on PowerPC. It seems that OS X 10.4 and 10.5 are
>> `git add -p' is your friend to do that conveniently.
>
> Sure, that is the usual suggestion. But I'm not sure if that is
> really helpful here because none of these changes will do anything
> on its own.
What do you mean with `none will do anything on its own'?
> So my question is whether th
Am Samstag, den 21.09.2019, 13:09 +0200 schrieb Werner LEMBERG:
> >> `git add -p' is your friend to do that conveniently.
>
> >
>
> > Sure, that is the usual suggestion. But I'm not sure if that is
>
> > really helpful here because none of these changes will do anything
>
> > on its own.
>
>
Jonas Hahnfeld via lilypond-devel writes:
> Am Samstag, den 21.09.2019, 13:09 +0200 schrieb Werner LEMBERG:
>> >> `git add -p' is your friend to do that conveniently.
>>
>> >
>>
>> > Sure, that is the usual suggestion. But I'm not sure if that is
>>
>> > really helpful here because none of th
>> 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
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
>
> > cha
> [...] 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.
LGTM, thanks.
Werner
___
lilypond-devel mailing list
lilypond-devel@
> I've also attached an image of rendering the old code (as present in
> the git) with a lilypond binary from current git.
For reference, here's an image of the original score.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://
Werner LEMBERG writes:
> Here's an updated version of the Stockhausen example, with a lot of
> added comments to the source code.
>
> I've also attached an image of rendering the old code (as present in
> the git) with a lilypond binary from current git.
[...]
Looking at the image, this appears
Am 21. September 2019 19:09:55 MESZ schrieb David Kastrup :
>Werner LEMBERG writes:
>
>> Here's an updated version of the Stockhausen example, with a lot of
>> added comments to the source code.
>>
>> I've also attached an image of rendering the old code (as present in
>> the git) with a lilypon
>> Here's an updated version of the Stockhausen example, with a lot of
>> added comments to the source code.
>
> Looking at the image, this appears more to the credit of LilyPond
> than Stockhausen. I have a hard time imagining a performer bringing
> this to life in a manner justifying the comple
>>I have a hard time imagining a performer bringing this to life in a
>>manner justifying the complexity written into the score.
>
> Why?
>
> It seems you haven"t heard enough of today"s highly qualified and
> dedicated performers ...
It's not about performing this notation. I'm sure this could
Hello,
On 21/09/2019 17:57, Werner LEMBERG wrote:
[...] 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.
LGTM, thanks.
Werner
20 matches
Mail list logo
