On 2019/10/29 22:00:09, Dan Eble wrote:
On 2019/10/29 19:38:39, hahnjo wrote: > Anyway, for now building the "latest" Python 2.4.6 is actually not
too hard.
... > This can be passed via PYTHON= to LilyPond's configure - > without any weird environment variables like LD_LIBRARY_PATH.
Should the lilypond configure script prefer to use the oldest
acceptable
version of Python that is installed? It looks like it currently tries
"python"
as its first choice and then works back from newer versions to older.
I think not. That GUB tends to use older versions is nothing we should subject downstream integrators to. It is more important that the official versions compile with newer Python versions than with older ones. At the same point, I agree that it is a nuisance that we sometimes detect GUB problems with a time delay and have to clean up. The usual way in which this happens is with add-on patches when the release fails. I would recommend not to go overboard in pretesting material but try to remember sticking to conservative syntax. A failure to run GUB is something we need to deal with eventually (either by updating dependencies or downgrading syntax) but it's not as much a showstopper for everybody than failure with current versions. https://codereview.appspot.com/573160047/
