Issue 1226 in lilypond: lilypond-book in the MinGW release is currently unusable (2.13.30?)

[lilypond]

Status: Accepted
Owner: ----
Labels: Type-Defect

New issue 1226 by RalphBugList: lilypond-book in the MinGW release is  
currently unusable (2.13.30?)
http://code.google.com/p/lilypond/issues/detail?id=1226


    Trevor Daniels wrote:


        The mingw binary of 2.13.30 gives the following error
        under Vista on my system:

        Running lilypond-book
        Traceback (most recent call last):
         File "c:/program files/lilypond/usr/bin/lilypond-book.py", line
        86, in ?
           import book_base as BookBase
         File "out/book_base.py", line 4, in ?
         File "out/book_snippets.py", line 9, in ?
         File "c:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py",
        line 352, in
         ?
           import msvcrt
        ImportError: No module named msvcrt
        Lilypond-book returned code 1

    2.13.23 is fine whereas 2.13.25 + higher have the above messages ( i  
haven't
    loaded 2.13.24)!

Reinhold's refactoring of lilypond-book modules was
first included in the 2.13.24 release, so this looks
a more likely cause.  He made a series of changes
terminating in commit 7d4265883794cec4ad0e7312f0787d0565fe757f
on 11 Jun 2010.