On 8/7/2019 2:03 PM, Gwyn Ciesla via bug-lilypond wrote:
when will Python 3 be supported?
After LilyPond's cross-build system gets taught how to build Python3 for
Windows. That will allow including it in LilyPond's Windows installer
binary, instead of needing users to resolve dependencies themselves.
Here are some past discussions on the topic. I gather the current
cross-build for Python did not come easily, and needed source code
patches that the Python project chose not to include upstream.
<https://lists.gnu.org/archive/html/lilypond-devel/2019-01/msg00082.html>
<https://lists.gnu.org/archive/html/lilypond-devel/2019-02/msg00099.html>
Pure speculation: I've seen installers for other software have multiple
stages. It's a single file still, but after it starts up and does some
preliminaries it says "Here comes the database backend now" and hands
off to a whole 'nother installer they included for something SQL, then
when that's done it returns to the original install.
I wonder how that approach compares to LilyPond's current practice for
Python? Could GUB's NSIS Windows-installer-builder portions bundle up
the stock Windows installer for Python? Looks like it would be ~26MB or
so. But for all I know, this idea may have already been considered and
rejected.
--
Karlin High
Missouri, USA
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
