| 1 |
Hi, everyone. |
| 2 |
|
| 3 |
TL;DR: we might keep Python 2.7 supported as a build-time dependency |
| 4 |
of a few packages as necessary, while removing the eclass support for |
| 5 |
installing packages for py2.7. |
| 6 |
|
| 7 |
|
| 8 |
As I've mentioned earlier, the plan is to get rid of Python 2.7 target |
| 9 |
support at the beginning of 2021. The plan was to last rite all |
| 10 |
remaining packages failing to support Python 3 at 2021-01-01, and remove |
| 11 |
the eclass support on 2021-02-15. At the same time, the Python |
| 12 |
interpreter was going to stay around for as long as necessary. |
| 13 |
|
| 14 |
I've also mentioned that there is a high risk that this will not be |
| 15 |
possible because of a few large entities ignoring the problem |
| 16 |
and failing to port their build system scripts away from Python 2. |
| 17 |
We can't really last rite all major web browsers, and postponing |
| 18 |
the deadline indefinitely is not a good solution either. |
| 19 |
|
| 20 |
Therefore, I advise the following plan B: if it is impossible to remove |
| 21 |
Python 2.7 support from packages entirely, the support for installing |
| 22 |
Python packages for Python 2.7 will be removed. However, there will be |
| 23 |
exemptions granted for build-time dependencies on the Python interpreter |
| 24 |
to keep things working, for as long as the interpreter itself is going |
| 25 |
to stay. |
| 26 |
|
| 27 |
The candidates for exemptions are pypy/pypy3 (CPython 2.7 is needed for |
| 28 |
bootstrap on new platforms), Mozilla products, WebKit and WebKit-based |
| 29 |
browsers. |
| 30 |
|
| 31 |
-- |
| 32 |
Best regards, |
| 33 |
Michał Górny |
Archives