[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Errors with midi2ly and musicxml2ly
From: |
address@hidden |
Subject: |
Re: Errors with midi2ly and musicxml2ly |
Date: |
Wed, 20 Nov 2019 18:41:41 +0100 |
Verzonden vanaf mijn Huawei mobiele telefoon
-------- Oorspronkelijk bericht --------
Onderwerp: Re: Errors with midi2ly and musicxml2ly
Van: address@hidden
Aan: Aaron Hill
Cc:
There are more python2 vs python3 issues in those scripts than just
that one. You can try to check ( and fix) using the 2to3 script.
Or use Python2 to run the scripts.
Verzonden vanaf mijn Huawei mobiele telefoon
-------- Oorspronkelijk bericht --------
Onderwerp: Re: Errors with midi2ly and musicxml2ly
Van: Aaron Hill
Aan: address@hidden
Cc:
On 2019-11-20 12:00 am, Артем Тартаковский wrote:
> ср, 20 нояб. 2019 г., 2:00 Aaron Hill :
>> It's a compatibility issue between Python 2 and 3. The backtick
>> operator was removed [1] in Python 3, in favor of the repr()
>> procedure.
>>
>> [1]:
>>
https://portingguide.readthedocs.io/en/latest/syntax.html#backticks
>>
>> It is my understanding the scripts shipping with LilyPond are not
>> expected to be interpretable by Python 3 yet.
>
> So what do I have to replace this construction with?
Near as I can tell, it's a simple replacement of `foo` with
repr(foo).
So, you could potentially run the scripts through the following sed
command:
sed -i~ 's/`\([^`]*\)`/repr(\1)/g' *.py
-- Aaron Hill
_______________________________________________
bug-lilypond mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Errors with midi2ly and musicxml2ly, Noeck, 2019/11/20