1 |
Signed-off-by: Michał Górny <mgorny@g.o> |
2 |
--- |
3 |
.../2020-02-06-python-2-7-eol.en.txt | 51 +++++++++++++++++++ |
4 |
1 file changed, 51 insertions(+) |
5 |
create mode 100644 2020-02-06-python-2-7-eol/2020-02-06-python-2-7-eol.en.txt |
6 |
|
7 |
diff --git a/2020-02-06-python-2-7-eol/2020-02-06-python-2-7-eol.en.txt b/2020-02-06-python-2-7-eol/2020-02-06-python-2-7-eol.en.txt |
8 |
new file mode 100644 |
9 |
index 0000000..6adc04e |
10 |
--- /dev/null |
11 |
+++ b/2020-02-06-python-2-7-eol/2020-02-06-python-2-7-eol.en.txt |
12 |
@@ -0,0 +1,51 @@ |
13 |
+Title: Python 2.7 went EOL |
14 |
+Author: Michał Górny <mgorny@g.o> |
15 |
+Posted: 2020-02-06 |
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. Python package |
21 |
+upstreams have started removing Python 2 compatibility code from their |
22 |
+packages more aggressively. This includes common dependencies such as |
23 |
+dev-python/pytest, dev-python/setuptools and dev-python/sphinx. While |
24 |
+we realize that many packages are still dependent on Python 2, providing |
25 |
+full support for it exceeds our maintenance capabilities. |
26 |
+ |
27 |
+Upstream is planning to make one more release of dev-lang/python:2.7 |
28 |
+in April 2020. We are going to continue maintaining and patching |
29 |
+the interpreter for as long as it is feasible, most likely even after |
30 |
+all Python 2 packages are gone from Gentoo. |
31 |
+ |
32 |
+At the same time, we are actively working towards switching |
33 |
+the distribution to Python 3. Whenever possible, we are removing |
34 |
+Python 2 support from packages. It will remain available for |
35 |
+the packages missing Python 3 compatibility and their dependencies |
36 |
+for some more time. However, packages that have little chances of being |
37 |
+ported will eventually be removed. |
38 |
+ |
39 |
+If you are still using Python 2 for your projects, we strongly recommend |
40 |
+you to migrate away. For the time being, it is preferable to use |
41 |
+dev-python/virtualenv or a similar solution rather than ebuilds, |
42 |
+to install the dependencies for your projects locally. |
43 |
+ |
44 |
+Regular Gentoo systems will be migrated off Python 2 gracefully. It may |
45 |
+be necessary to use --changed-deps or a similar option during system |
46 |
+upgrades whenever they become blocked by Python 2 packages installed |
47 |
+earlier. |
48 |
+ |
49 |
+If you wish to remove Python 2.7 entirely sooner, you can try removing |
50 |
+python2_7 from PYTHON_TARGETS. However, this will require adding |
51 |
+explicit package.use entries if some of the installed packages still |
52 |
+require Python 2. An example package.use entry follows: |
53 |
+ |
54 |
+ # disable py2.7 without altering the other flags |
55 |
+ */* PYTHON_TARGETS: -python2_7 |
56 |
+ # enable py2.7 for setuptools |
57 |
+ dev-python/setuptools PYTHON_TARGETS: python2_7 |
58 |
+ # switch a single-impl package to 2.7 |
59 |
+ dev-embedded/libftdi PYTHON_TARGETS: python2_7 |
60 |
+ dev-embedded/libftdi PYTHON_SINGLE_TARGET: -* python2_7 |
61 |
+ |
62 |
+Note that package.use entries are not necessary for packages that |
63 |
+support one implementation only (i.e. do not support Python 3 at all). |
64 |
-- |
65 |
2.25.0 |