On Sun, Mar 16, 2014 at 04:41:46PM -0400, Julien Rioux wrote: > I think the following would be a good 1-2 punch approach for the > current development cycle: First, upgrade python in GUB and make > sure we can build current dev and stable branches of lilypond from > it. Then bump the python requirement in the dev branch and start > migrating to a codebase that supports python 2.6+ and python 3+
Sounds great! Thanks for working on this. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
