Re: musicxml2ly, midi2ly etc. broken ?

[Ole Schmidt]

Am 10.10.2010 um 19:37 schrieb James Bailey:

> 
> On Oct 10, 2010, at 7:14 PM, Valentin Villenave wrote:
> 
>> 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.
> 
> I had no problems with convert-ly. I guess I'll add midi2ly and musicxml to 
> my prerelease checklist.

I just checked convert-ly and musicxml2y- both work fine here with 2.13.35 and 
with 2.12.3 (on a MacBook Pro 3,1   with Mac OS X 10.6.4)

ole