Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: gentoo-dev@l.g.o
Cc: python@g.o, "Michał Górny" <mgorny@g.o>
Subject: [gentoo-dev] [REVIEW v2 1/2] 2020-09-28-python-2-7-cleanup: add a new news item
Date: Mon, 28 Sep 2020 06:43:29
Message-Id: 20200928064256.124822-2-mgorny@gentoo.org
In Reply to: [gentoo-dev] [REVIEW v2 0/2] 2020-09-28-python-2-7-cleanup news item by "Michał Górny"
1 Signed-off-by: Michał Górny <mgorny@g.o>
2 ---
3 .../2020-09-28-python-2-7-cleanup.en.txt | 58 +++++++++++++++++++
4 1 file changed, 58 insertions(+)
5 create mode 100644 2020-09-28-python-2-7-cleanup/2020-09-28-python-2-7-cleanup.en.txt
6
7 diff --git a/2020-09-28-python-2-7-cleanup/2020-09-28-python-2-7-cleanup.en.txt b/2020-09-28-python-2-7-cleanup/2020-09-28-python-2-7-cleanup.en.txt
8 new file mode 100644
9 index 0000000..8dbcd78
10 --- /dev/null
11 +++ b/2020-09-28-python-2-7-cleanup/2020-09-28-python-2-7-cleanup.en.txt
12 @@ -0,0 +1,58 @@
13 +Title: Python 2.7 cleanup is progressing
14 +Author: Michał Górny <mgorny@g.o>
15 +Posted: 2020-09-28
16 +Revision: 1
17 +News-Item-Format: 2.0
18 +Display-If-Installed: dev-lang/python:2.7
19 +
20 +Python 2.7 has reached its end-of-life by 2019-12-31, and many projects
21 +have removed Python 2 support since. During the last few months we have
22 +been working hard to migrate Gentoo to Python 3, and we have finally
23 +reached the point making it possible for the vast majority of our users
24 +to run a system free of Python 2.7 modules.
25 +
26 +The few remaining high profile packages (e.g. dev-python/cython)
27 +are preserving Python 2.7 only for a very few uncommon packages.
28 +For this reason, we have decided to create new revisions of them having
29 +Python 2.7 removed. If you do not need Python 2.7 there, your package
30 +manager should upgrade these packages to the new revisions.
31 +
32 +Please note that you may need to manually uninstall any Python 2.7
33 +packages installed from third-party repositories and/or run `emerge
34 +--depclean` first to remove orphan packages. The recommended process
35 +for Portage users is:
36 +
37 + emerge --depclean
38 + emerge -vDuU @world
39 + emerge --depclean
40 +
41 +Please note that the Python 2.7 interpreter (without additional Python
42 +packages) remains necessary to build a few high profile packages,
43 +in particular Chromium, Mozilla software and PyPy. If you build either
44 +of these packages from source, you will not be able to permanently
45 +remove Python 2.7 from your system.
46 +
47 +We are going to preserve CPython 2.7 (and PyPy2.7) for as long
48 +as necessary and provide security fixes to the best of our ability.
49 +However, please note that we are not able to dedicate resources to
50 +auditing Python 2.7's code and with little community interest in that,
51 +it should be considered potentially vulnerable.
52 +
53 +If your projects still rely on Python 2.7, we would like to once again
54 +encourage you to migrate them to Python 3. However, if you really need
55 +to run them, we suggest using a virtualenv. To create a new Python 2.7
56 +environment, install dev-python/virtualenv and use the following option:
57 +
58 + virtualenv -p /usr/bin/python2.7 ...
59 +
60 +To create a PyPy2.7 environment:
61 +
62 + virtualenv -p /usr/bin/pypy ...
63 +
64 +Modern versions of pip should be able to automatically select older
65 +versions of packages that still support Python 2.7. Please note that
66 +these versions are generally no longer supported. They can be buggy,
67 +vulnerable or simply incompatible with one another.
68 +
69 +Please do not forget to add dev-lang/python:2.7 to your @world set
70 +or it may get depcleaned once all package dependencies are gone.
71 --
72 2.28.0