Date: Sun, 19 Apr 2020 21:40:11 +0200 From: Martin Neubauer <m.ne@gmx.net> To: freebsd-ports@freebsd.org Subject: Re: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available Message-ID: <0d2adba2-2a8e-3960-90c3-193f62420b6f@gmx.net> In-Reply-To: <86685354-ea84-6ea4-e230-51cef83fd803@druid.net> References: <CAGnMC6rNeUT2wQ=DsrvkNtVz_SGqfKA8Yh=1rbeMS8XtxB3naw@mail.gmail.com> <102F7F34-78D0-45D8-A6CD-54C90BD46791@FreeBSD.org> <24218.18351.39302.604589@jerusalem.litteratus.org> <b16f5e5c-5283-9a14-b738-eff635c14109@m5p.com> <24218.25496.502886.46431@jerusalem.litteratus.org> <bb862ff4-33f2-f5af-450a-72a33105759e@FreeBSD.org> <20200418090615.jl25cg3jhzcdrkcb@ozzmosis.com> <86685354-ea84-6ea4-e230-51cef83fd803@druid.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3MecXr8dMb3QVRnojLe63i4OF6kciZoSL Content-Type: multipart/mixed; boundary="9e2TsYd9rtR4tg8s6seEpvLhFYOeBoR4H" --9e2TsYd9rtR4tg8s6seEpvLhFYOeBoR4H Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 18/04/2020 11:57, D'Arcy Cain wrote: > I tried building lilypond with python2.7 removed from USES but its > configure script failed due to Python < 3.0. I couldn't find any > discussion about upgrading the version of Python but WikipediA says tha= t > it has 120,000 lines Python code. As far as I can tell there is nothin= g > as good as Lilypond for engraving music. It would be quite a blow to > musicians if that was removed. I think I can reassure you that lilypond isn't going away (at least not because of the Python 2 vs. 3 issue.) Currently I'm maintaining lilypond-devel and have already created a patch updating to 2.21.0 not depending on Python 2 any more. I've already planned to take care of updating lilypond to 2.20.0 as soon as I'll be able to. Maybe that would mean backporting the upstream changeset switching to Python 3. (The change was done well before the 2.20.0 release, but it seems to only be present in the 2.21 branch. Luckily the changes are fairly trivial, but because so many files are touched still would mean quite some legwork.) Regards, Martin --=20 X is a large contribution. --9e2TsYd9rtR4tg8s6seEpvLhFYOeBoR4H-- --3MecXr8dMb3QVRnojLe63i4OF6kciZoSL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEMHVrsqKu60F5jvxaoBLYqhRr9C0FAl6cqSQACgkQoBLYqhRr 9C2qQBAAm5D4xQ7YYNMAux6DpBwiJWc2fLURKljqft0VrwwP4TL/e39kdcVQCZ0x 2DKfLqCFdbqMSwik0VtobE0BpTxV15+cVerMRHdg3kefXy4CSniQIBEr6SmxYS3K RIo4xYfbQEaVYTP5jUZa9sJ+lyMCxqz5Qnx0btsIxCjgZyQ+YLyCagPrB/LjuQ5D oZfRtPcVlWJ7+2zmd2ULyVFIPWQNy/QnH1BqUt8RaQ8LbgUp7KNxwSxxEnQnMPeS I4SgfmWaKFe3TUIXQXlFKbJZ0uxhllefg2JftlxepG5x06HJKZgIhiwc7XpKi+3q kq6qO/ClcJjw1N6IGzBIZH2eTyNl0tXC+wmSTkLDzAfw8mWhZuS4FVskBZwlHTEH rAAiXv/8Ib5NS+3SIm+K+Frex951+mkhnbjGhFAYrp2095HEvwN7hjKzzLTAeeJV ZOsaQGaeOwx1Zb5JDGiW32LV6pyQlBdd662ekCqaAzSXIXhypKLczEPEXRm+jS/E KUWR/s++6Qo0cMPEVh5MFpVLaHTjhRcaT5f8Umsa3gnE8qrFbRT8/AHh5QIhAuYh SYQUdy7iZO9uhiGRCsDHyEp4wNIgtCdT3IdEUmcAV3DuWFd/WU19fOAt733yK675 9Gk5LC/C6OXRwnCxm4uJbmwAJa/n3BePszhlZt+YJqyQ4+vcuVE= =M3uS -----END PGP SIGNATURE----- --3MecXr8dMb3QVRnojLe63i4OF6kciZoSL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0d2adba2-2a8e-3960-90c3-193f62420b6f>