1 |
W dniu wto, 15.05.2018 o godzinie 08∶20 +0200, użytkownik Michał Górny |
2 |
napisał: |
3 |
> Hello, everyone. |
4 |
> |
5 |
> Please review the following news item. The 'xx'-es will be replaced with |
6 |
> the publication date, making the deadline appropriately pub + 1 month. |
7 |
> |
8 |
> --- |
9 |
> Title: Python 3.6 to become the default target |
10 |
> Author: Michał Górny <mgorny@g.o> |
11 |
> Posted: 2018-05-xx |
12 |
> Revision: 1 |
13 |
> News-Item-Format: 2.0 |
14 |
> Display-If-Installed: dev-lang/python:3.5 |
15 |
> |
16 |
> On 2018-06-xx, Python 3.6 will replace Python 3.5 in the default Python |
17 |
> targets for Gentoo systems. The new default targets will be: |
18 |
> |
19 |
> PYTHON_TARGETS="python2_7 python3_6" |
20 |
> PYTHON_SINGLE_TARGET="python3_6" |
21 |
> |
22 |
> If you have not overriden the value of those variables on your system, |
23 |
> then your package manager will want to use the new targets immediately. |
24 |
> In order to prevent dependency conflicts, please clean stray packages |
25 |
> and rebuild/upgrade all packages with USE flag changes after the change, |
26 |
> e.g.: |
27 |
> |
28 |
> emerge --depclean |
29 |
> emerge -1vUD @world |
30 |
> emerge --depclean |
31 |
> |
32 |
> Please note that upgrading dependencies in place may cause some |
33 |
> of the package dependencies to be temporarily missing. While this |
34 |
> should not affect scripts that are already fully loaded, it may cause |
35 |
> ImportErrors while starting Python scripts or loading additional |
36 |
> modules (only scripts running Python 3.5 are affected). |
37 |
> |
38 |
> In order to improve stability of the upgrade, you may choose to |
39 |
> temporarily enable both targets, i.e. set in /etc/portage/make.conf |
40 |
> or its equivalent: |
41 |
> |
42 |
> PYTHON_TARGETS="python2_7 python3_5 python3_6" |
43 |
> PYTHON_SINGLE_TARGET="python3_5" |
44 |
> |
45 |
> This will cause the dependencies to include both Python 3.5 and 3.6 |
46 |
> support on the next system upgrade. Once all packages are updated, |
47 |
> you can restart your scripts, remove the custom setting and run another |
48 |
> upgrade to remove support for Python 3.5. |
49 |
> |
50 |
> If you would like to postpone the switch to Python 3.6, you can copy |
51 |
> the current value of PYTHON_TARGETS and/or PYTHON_SINGLE_TARGET |
52 |
> to /etc/portage/make.conf or its equivalent: |
53 |
> |
54 |
> PYTHON_TARGETS="python2_7 python3_5" |
55 |
> PYTHON_SINGLE_TARGET="python3_5" |
56 |
> |
57 |
> If you would like to migrate your systems earlier, you can do the same |
58 |
> with the new value. |
59 |
> |
60 |
> If you are still using Python 3.4, please consider switching to a newer |
61 |
> version as it is reaching its end-of-life. The end-of-life dates |
62 |
> for the currently used versions are: |
63 |
> |
64 |
> Python 3.4 2019-03-16 |
65 |
> Python 2.7 2020-01-01 |
66 |
> Python 3.5 2020-09-13 [1] |
67 |
> |
68 |
> [1]:https://devguide.python.org/#status-of-python-branches |
69 |
> |
70 |
|
71 |
Finally committed it. This puts the deadline at 2018-06-22. |
72 |
Also included users using python:3.4. |
73 |
|
74 |
-- |
75 |
Best regards, |
76 |
Michał Górny |