On Sun, Aug 26, 2012 at 11:14:06AM +0100, Phil Holmes wrote: > ----- Original Message ----- From: "Martin Tarenskeen" > <[email protected]> > To: "lilypond-devel mailinglist" <[email protected]> > > >Also I was hoping to find info about the required/recommended > >Python version here when I was browsing the docs. Maybe that info > >can be found somewhere else? > > It looks like the Python on my windows install is 2.4.5.
Yes. All lilypond scripts must work on python 2.4.5 or maybe even 2.4.2. This causes problems because everybody uses+tests stuff with python 2.6 or 2.7, and we only discover the 2.4.5 problem while building the binaries. > >BTW: Are there any thoughts about switching from Python 2.x to > >Python 3.x somewhere in the future? > > I don't believe so. A lot of the GUB build relies on Python, and it > also creates a shipping Python by a mechanism I don't believe anyone > currently understands. Is there a good reason to want to? Jan and John have spent most of the past 2 days working on GUB side-by-side, and they're likely to spend most of today doing the same. Changing to python 3 would be far more intrusive than updating to python 2.7, but even python 2.7 is likely out of reach from a mere 4 days of solid work from two of our best build system hackers. If anybody's interested in this stuff, then please check out the GUB repo. Right now all work is done on the Waltrop branch, but we'll be merging that with master soon. - Graham _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
