>> @Werner: Didn't you write something about updating python in gub?
Well, someone (I forgot his name) offered to work on updating python
to the latest 2.7.x version, which should make it easier to eventually
migrate to python 3.x...
> I assume you're referring to the situation that (e.g.)
Le vendredi 08 février 2019 à 22:19 +0100, Werner LEMBERG a écrit :
> > - addition of texinfo/txi-pt.tex from Texinfo sources, as
> Portuguese
> > translation has been added and I don't have Texinfo installed in
> GUB
> > host system;
>
> ??? What exactly needs Portuguese? Lilypond doesn't,
Hi,
--
5e44fec38f33997109bc85c099472b2736649fde is the first bad commit
commit 5e44fec38f33997109bc85c099472b2736649fde
Author: Frederic Gohier
Date: Thu May 10 11:12:44 2018 +0100
Fix
For more than 10 years gub/specs/lilypond.py used /usr/bin/python.
That means that during lilypond-test the system's python interpreter
is used as the interpreter for the musicxml2ly script, not our own
python in target/tools. At some currently unknown point in time
musicxml2ly became
On my system, your description matches: Current Master's musicxml2ly
python script runs fine using my local python2 (2.7.15rc1) but has
the error using 2.19.82's python2.4 (2.4.5).
Given that nobody is really working on musicxml2ly, I strongly suggest
that people start testing and using
Lukas-Fabian Moser writes:
>>> For more than 10 years gub/specs/lilypond.py used
>>> /usr/bin/python. That means that during lilypond-test the system's
>>> python interpreter is used as the interpreter for the musicxml2ly
>>> script, not our own python in target/tools. At some currently
>>>
Folks,
attached are two images that show my planned documentation of
lilypond's binary relocation. What I'm interested in are comments to
the relocation algorithm. If we can find an agreement, I'm going to
fix lilypond to follow it.[*] Right now, lilypond's behaviour is quite
erratic and has
>> I'd rather do this in the opposite order and put #4 and #5 (as "Use
>> VAR_FOODIR as LilyPond FOO directory) just after #1, and execute #2
>> only if LILYPOND_DATADIR environment variable is unset.
>
> Good idea, thanks.
Here's an updated version of the algorithm, which is now pretty
simple
>> What I'm interested in are comments to the relocation algorithm.
>> If we can find an agreement, I'm going to fix lilypond to follow
>> it.[*]
>
> Is there a good reason for looking for $INSTALLER_PREFIX
> subdirectories (#2) before examining whether LILYPOND_DATADIR and
> LILYPOND_LOCALEDIR
Le samedi 09 février 2019 à 20:56 +0100, Werner LEMBERG a écrit :
> attached are two images that show my planned documentation of
> lilypond's binary relocation. What I'm interested in are comments to
> the relocation algorithm. If we can find an agreement, I'm going to
> fix lilypond to follow
Hi everybody,
For more than 10 years gub/specs/lilypond.py used /usr/bin/python.
That means that during lilypond-test the system's python interpreter
is used as the interpreter for the musicxml2ly script, not our own
python in target/tools. At some currently unknown point in time
11 matches
Mail list logo
