Re: New lilypond-book error message in 7.2.39, mingw

[Han-Wen Nienhuys]

Mats Bengtsson wrote:
> Running lilypond-book fromversion 2.7.39 in Windows now results in:
>
> Traceback (most recent call last):
>  File "C:\Program Files\LilyPond\usr\bin\lilypond-book.py", line 75, in ?
>    import lilylib as ly
>  File "out/lilylib.py", line 17, in ?
>  File "C:\Program Files\LilyPond\usr\lib\python2.4\subprocess.py", line 
> 377, in
> ?
>    import fcntl
> ImportError: No module named fcntl

> I don't really understand why we could not include the full subprocess
> module in the Python included in the lilypond package. It's included in 
> the native Windows version of Python available at www.python.org, so it's
> certainly not impossible.

The problem is that we're cross compiling Python from linux for mingw, 
which highly unorthodox method. Hopefully, we'll be able to work with 
the python community to put saner cross-compiling patches into Python.

> Regarding the other remaining lilypond-book + Windows related bug, the 
> following hack is one possible solution. A cleaner solution is
> probably to send the arguments as a sequence to subprocess.Popen, which 
> avoids all problems with quoting arguments. However, then the -P flag to 
> lilypond-book won't work of you want to supply arguments there.

I don't understand; AFAIK, the cygwin bash shell should handle quoting 
in the same was as the unix bash shell. It's possible to use quotes with 
the Windows  shell, but that is highly unportable; every flavor of 
windows uses the quotes in a different way. I'd recommend just using Cygwin.

--

Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com