[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilypond-book is not flavor independent

From: Graham Percival
Subject: Re: lilypond-book is not flavor independent
Date: Sat, 28 Mar 2009 20:18:57 +0800
User-agent: Mutt/1.5.18 (2008-05-17)

On Sat, Mar 28, 2009 at 12:08:27PM +0000, Cláudia Soares wrote:
> On 2009/03/28, at 11:54, Graham Percival wrote:
>> The only problem is that we don't distribute python for OSX, and
>> OSX has its own issues with python.  I'm not certain /why/ we
>> don't ship python on OSX, but I *am* certain that it's too
>> complicated for me to fix at the moment.
> That's a much better explanation. Thanks.
>  I don't quite like to have all the apps shipping their own favorite  
> interpreter version... Why not force a version in the path? like
> #!/usr/bin/env python2.4

That's fine, as long as everybody has python installed.  Now, I'd
be surprised[1] if we found any desktop Linux machines without
python... but there's no guarantees that everybody has the python
version we want.  For example, this Debian Lenny laptop only has

[1]  although /I'd/ be surprised, clearly the much-wiser-than-me
people who wrote the cross-platform builder thought it could be an
issue, and I'm happy to trust their judgement over mine in this
regard.  :)

> Nevertheless, I can work on that issue concerning the mac osx lilypond. I 
> have one tiger ppc and one leopard intel, so i'll check compat for both 
> OSes and architectures.

That would be great!  Leopard has python 2.5.1 by default, so
there's no problem there.  Tiger uses 2.3.5, which does *not*
support lilypond-book and convert-ly.
(we use set(), which was introduced in python 2.4)

I've made about half a dozen posts on this subject over the past
year or two; it might be useful to read one or two of those

> Can someone point me to the code's development branch?


in particular:
(the gub link)

The last link is the most important one.

Good luck!
- Graham

reply via email to

[Prev in Thread] Current Thread [Next in Thread]