|
From: | Trevor Daniels |
Subject: | Re: Problem with 2.13.30? |
Date: | Mon, 16 Aug 2010 23:09:48 +0100 |
Eluze wrote Sunday, August 15, 2010 10:20 AM
Trevor Daniels wrote:2.13.23 is fine whereas 2.13.25 + higher have the above messages ( i haven'tThe 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 1loaded 2.13.24)!
Thanks Eluze. To help track this down, 2.13.23 was built on 3 Jun 2010 2.13.24 was built on 14 Jun 2010 2.13.25 was built on 20 Jun 2010 Jan's change to MinGW as reported by Patrick:
This could be related to Jan's recent changes to the MinGW Python build in GUB. Something related to "msvcrt" was added here: http://github.com/janneke/gub/commit/e3d46689d881045ceb2dbf31d7d4573709f781d8#L1R136
was made on 18 Jul 2010, so this can't be the cause. 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. Bug-squad: can you please raise an issue for this. lilypond-book in the MinGW release is currently unusable. Trevor
[Prev in Thread] | Current Thread | [Next in Thread] |