public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev-announce] Python 2.7 cleanup: plan B
Date: Tue, 11 Aug 2020 18:30:57 +0200	[thread overview]
Message-ID: <5085bdf5cba4d2807ad3fa0c6e25be02188fcc94.camel@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]

Hi, everyone.

TL;DR: we might keep Python 2.7 supported as a build-time dependency
of a few packages as necessary, while removing the eclass support for
installing packages for py2.7.


As I've mentioned earlier, the plan is to get rid of Python 2.7 target
support at the beginning of 2021.  The plan was to last rite all
remaining packages failing to support Python 3 at 2021-01-01, and remove
the eclass support on 2021-02-15.  At the same time, the Python
interpreter was going to stay around for as long as necessary.

I've also mentioned that there is a high risk that this will not be
possible because of a few large entities ignoring the problem
and failing to port their build system scripts away from Python 2.
We can't really last rite all major web browsers, and postponing
the deadline indefinitely is not a good solution either.

Therefore, I advise the following plan B: if it is impossible to remove
Python 2.7 support from packages entirely, the support for installing
Python packages for Python 2.7 will be removed.  However, there will be
exemptions granted for build-time dependencies on the Python interpreter
to keep things working, for as long as the interpreter itself is going
to stay.

The candidates for exemptions are pypy/pypy3 (CPython 2.7 is needed for
bootstrap on new platforms), Mozilla products, WebKit and WebKit-based
browsers.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

                 reply	other threads:[~2020-08-11 17:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5085bdf5cba4d2807ad3fa0c6e25be02188fcc94.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox