lilypond-user
[Top][All Lists]
Advanced

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

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0


From: David Kastrup
Subject: Re: Python 3, was Re: ANN: Frescobaldi 2.19.0
Date: Sun, 24 Apr 2016 17:54:52 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

Paul Morris <address@hidden> writes:

>> On Apr 24, 2016, at 11:15 AM, David Kastrup <address@hidden> wrote:
>> 
>> Paul Morris <address@hidden> writes:
>> 
>>> IIUC, wouldn’t the first step be, in any case, to get LilyPond’s
>>> python scripts working on python 2.7?
>> 
>> Which ones _aren't_ working with Python 2.7?  I run a number of them
>> routinely, and I just converted some file with midi2ly as well.
>
> Sorry, my words weren’t very precise.  I don’t know of any scripts
> that aren’t working with 2.7.
>
> I jus wanted to make the point that since the LilyPond binaries ship
> with an earlier python version and that GUB still uses 2.4 (as
> mentioned earlier in the thread) that getting those things
> successfully upgraded to python 2.7 would be the first step to take
> (regardless of how we handle the transition to python 3).

No disagreement here.  At the very least it would be verification that
the ones responsible for doing the GUB part of the transition are
comfortable with the basic necessities.

> (Of course, you’re right that the transition to guile 2 is a much
> higher priority, but it seems we could use any help we can get
> wherever we can get it.)

I don't see that those tasks are competing for the same developers.

-- 
David Kastrup



reply via email to

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