|
From: | Knut Petersen |
Subject: | Re: issues with musicxml2ly |
Date: | Mon, 15 Jul 2019 15:44:51 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 |
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.5This leads me to two questions: a) What's the reason for shipping it's own python interpreter on linux?
We want to provide easy to use installers that provide all the needed software for all the supported platforms. Using the same python on all platforms might help to reduce effects of incompatibilities. A relatively new reason: Python2 will be phased out by upstream really soon ;-)
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 ;-) Knut
[Prev in Thread] | Current Thread | [Next in Thread] |