Graham, you wrote Friday, January 13, 2012 8:41 AM
As a cheap experiment, could you add this:
### EXPERIMENTAL HACK: see if this makes mingw behave better?
time.sleep(1)
immediately between the
proc = ...
and
(parameter_string, error_string) = proc.communicate ()
lines?
oh, and add
On Fri, Jan 13, 2012 at 08:41:14AM +, Graham Percival wrote:
> I don't expect it to work, so I'm writing a more intrusive hack to
> hopefully avoid this... but I'd be delighted to junk the larger
> hack if that can make it work.
sorry, ignore that. I'm building a new binary with a better fix,
On Thu, Jan 12, 2012 at 09:02:51AM -, Trevor Daniels wrote:
>
> IOError: (0, 'Error')
> Lilypond-book returned code 1
Thanks, working on fixes.
As a cheap experiment, could you add this:
### EXPERIMENTAL HACK: see if this makes mingw behave better?
time.sleep(1)
immediately between t
Graham, you wrote Thursday, January 12, 2012 6:22 AM
I expect to have that sleep(0.001) error. I do not expect any
other errors.
http://lilypond.org/~graham/lilypond-2.15.25-2.mingw.exe
What's the exact error you see when you try this one? I
know/expect that it barfs in threading.py, but I
I expect to have that sleep(0.001) error. I do not expect any
other errors.
http://lilypond.org/~graham/lilypond-2.15.25-2.mingw.exe
What's the exact error you see when you try this one? I
know/expect that it barfs in threading.py, but I need to know what
in the lilypond code calls that.
Cheer
