Re: Fwd: Binaries of LilyPond 2.23.5 with Guile 2.2

[Michael Käppler]

Am 16.12.2021 um 08:00 schrieb Jonas Hahnfeld via Discussions on
LilyPond development:
> Am Donnerstag, dem 16.12.2021 um 00:11 +0100 schrieb Robin Bannister:
> > A few hours ago I wrote (re 2.23.5fixed)
> > > Well, initially I ran into irrelevancies because my .ly file (for 2.22)
> > > has #on-the-fly, which is no longer acceptable.
> > >
> > > I tried running convert-ly.py, but it was missing a .dll.
> > > I will detail this later.
> > The attached file details this in its Case 1.
> >
> > Case 2 is a workround using the 2.23.5 (1.8) system's python.
> Ah yes: https://bugs.python.org/issue40740
> So while we could technically stick to Python 3.8 for now, I'd argue
> that Windows 7 is EOL since 2015, extended support ended almost two
> years now (January 14, 2020). In my opinion, it doesn't make sense for
> an open-source project to continue active support.
If switching back to Python 3.8 would be the only thing needed to
continue support
for Windows 7, I would strongly suggest doing that. My gut feeling is
that many active musicians
are very interested in getting new, critical editions of _music_, but
are rather conservative with regard
to their technical setup ;)
There are not few "features" that Microsoft introduced during the last
Windows editions that tend to annoy users
more than their awareness for security risks could compensate.

Michael