[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond code/feature freeze for 2.12
From: |
Valentin Villenave |
Subject: |
Re: Lilypond code/feature freeze for 2.12 |
Date: |
Mon, 29 Sep 2008 16:46:54 +0200 |
2008/9/29 John Mandereau <address@hidden>:
> I don't understand the point; warning the user is better than printing a
> Python traceback, isn't it? Using the right Python version for our
> scripts among those installed is another issue, which we can only deal
> with in the documentation, as we don't ship Python in MacOS binaries.
Just a (silly) question btw: why don't we? Can't we? Won't we?
Cheers,
Valentin
Re: Lilypond code/feature freeze for 2.12, Trevor Daniels, 2008/09/23
Re: Lilypond code/feature freeze for 2.12, Mark Polesky, 2008/09/22
Re: Lilypond code/feature freeze for 2.12, Matthias Neeracher, 2008/09/22
- Re: Lilypond code/feature freeze for 2.12, John Mandereau, 2008/09/22
- Re: Lilypond code/feature freeze for 2.12, Matthias Neeracher, 2008/09/22
- Re: Lilypond code/feature freeze for 2.12, John Mandereau, 2008/09/29
- Re: Lilypond code/feature freeze for 2.12,
Valentin Villenave <=
- Re: Lilypond code/feature freeze for 2.12, John Mandereau, 2008/09/29
- Re: Lilypond code/feature freeze for 2.12, Valentin Villenave, 2008/09/29
- Re: Lilypond code/feature freeze for 2.12, Han-Wen Nienhuys, 2008/09/29
Re: Lilypond code/feature freeze for 2.12, Trevor Daniels, 2008/09/23
Re: Lilypond code/feature freeze for 2.12, Carl Sorensen, 2008/09/23
Re: Lilypond code/feature freeze for 2.12, Trevor Daniels, 2008/09/23