On Sat, Apr 05, 2014 at 08:53:04AM +0200, David Kastrup wrote: > Jan Nieuwenhuizen <jann...@gnu.org> writes: > > > David Kastrup writes: > > > >> So my first impulse would be to throw out the workaround for 2.4.2 that > > > > Let's do that. > > Well, issue 1933 > <URL:http://code.google.com/p/lilypond/issues/detail?id=1933> would > suggest that this is a bad idea. Nothing substantially has changed > since then. I'm currently trying to get the TEXINPUTS stuff integrated > into the Mingw fix to arrive back at a working lilypond-book, but of > course it is to be hoped that moving Python forward to 2.6 might make > that problem go away. But it will take longer to figure that out.
Doesn't Julien have GUB with python 2.6 ready for testing? I would move forward on that before diving into the dark waters of os.popen in python 2.4. I remember bug 1933; it was really annoying. Cheers, - Graham _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
