[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: musicxml2ly, midi2ly etc. broken ?
From: |
Valentin Villenave |
Subject: |
Re: musicxml2ly, midi2ly etc. broken ? |
Date: |
Sun, 10 Oct 2010 19:14:36 +0200 |
On Sun, Oct 10, 2010 at 6:21 PM, James Bailey
<address@hidden> wrote:
> On 10.6.4, I get this error:
> RuntimeWarning: Python C API version mismatch for module midi: This Python
> has API version 1013, module midi has version 1012
> But I do get a lilypond file produced, version 2.7.18…
>
> I should note that this file cannot be processed as-is; the oldest supported
> is 2.7.38, but convert-ly runs just fine, and it compiles afterwards.
Sorry, I should have read this mail before answering your former mail :)
No Python path problem then? I'll open a separate issue for the midi
module (also reported by Ole, albeit with a twist): added as
http://code.google.com/p/lilypond/issues/detail?id=1318
That being said, I'd be curious to see whether the convert-ly/Python
path issue can be reproduced.
Valentin.
- Re: musicxml2ly, midi2ly etc. broken ?, Valentin Villenave, 2010/10/10
- Re: musicxml2ly, midi2ly etc. broken ?, Valentin Villenave, 2010/10/10
- Re: musicxml2ly, midi2ly etc. broken ?, James Bailey, 2010/10/10
- Re: musicxml2ly, midi2ly etc. broken ?,
Valentin Villenave <=
- Re: musicxml2ly, midi2ly etc. broken ?, James Bailey, 2010/10/10
- Re: musicxml2ly, midi2ly etc. broken ?, Ole Schmidt, 2010/10/11
- Re: musicxml2ly, midi2ly etc. broken ?, Valentin Villenave, 2010/10/10
Re: musicxml2ly, midi2ly etc. broken ?, James Bailey, 2010/10/10
Re: musicxml2ly, midi2ly etc. broken ?, Ole Schmidt, 2010/10/11