Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again

[lilypond]

Comment #34 on issue 1933 by address@hidden: Lilypond-book requires  
msvcrt again
http://code.google.com/p/lilypond/issues/detail?id=1933

No - that's a really good question.  I only have wine at home, but I'll try  
my best to finagle a version of LilyPond on it that uses the binary from  
python.org.  It is entirely possible that the errors come from  
lilypond-book and not Python at all: I think that running a test like this  
will help a great deal.  If anyone else can do this, please lemme know.   
Irrespective of whether or not we decide to scrap Python, running  
lilypond-book against different Python binaries is a good way to know how  
where in the debugging chain we need to look.

As for the "not cause any others", that's also a good question: I'm not  
sure.  I'm banking on this version of Python being more stable than one  
that we could brew ourselves, but that is a hunch.  I'll do my best to test  
tomorrow.

I would recommend Python 2.7.