Hi Michael!
b) Is there work on migrationg to Python3?
I don't think so.
Python2 will be phased out by upstream really soon now.
Yes. We know. No problem If we have our own python2 ;-)
Sad to hear that.
If I find time I'll have a look into it.
Porting to Python3 is relatively doable in my e
YESS
--
Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
There seems to be a problem with the \bendAfter command which is affected when
used with chords, even in another voice. Not sure what's going on here.
%
\version "2.19.83"
{
\textLengthOn
c''1\bendAfter #-5 ^"this bend OK"
^"no bend attem
On 7/15/2019 8:59 AM, Michael Kesper wrote:
If I find time I'll have a look into it.
Porting to Python3 is relatively doable in my experience.
A few other people have expressed interest in working on Python
upgrades. Past discussions indicated that the biggest challenges would
be getting GUB
Hi Knut,
On 15.07.19 15:44, Knut Petersen wrote:
> On 15.07.19 09:34, Michael Kesper wrote:
>> b) Is there work on migrationg to Python3?
> I don't think so.
>
>> Python2 will be phased out by upstream really soon now.
>
> Yes. We know. No problem If we have our own python2 ;-)
Sad to hear that
On 15.07.19 09:34, Michael Kesper wrote:
Hi all,
On 14.07.19 22:59, Knut Petersen wrote:
Bug 1:
Musicxml2ly is incompatible to the python2 distributed with the installers.
Musicxml2ly needs at least python2 2.7.0, lilypond installers provide python
2.4.5
This leads me to two questions:
a) Wh
Hi all,
On 14.07.19 22:59, Knut Petersen wrote:
> Bug 1:
> Musicxml2ly is incompatible to the python2 distributed with the installers.
> Musicxml2ly needs at least python2 2.7.0, lilypond installers provide python
> 2.4.5
This leads me to two questions:
a) What's the reason for shipping it's ow
