1 |
On Sun, Dec 8, 2019 at 9:38 AM Dale <rdalek1967@×××××.com> wrote: |
2 |
> |
3 |
> The best I can come up with, start figuring out a way to keep python 2 |
4 |
> around on your own, use a overlay if one is available or start expecting |
5 |
> python 2 to disappear, real soon. It seems the devs want it gone even |
6 |
> before it's end of life. |
7 |
> |
8 |
|
9 |
Nobody really wants it gone per se. It is just that nobody has |
10 |
stepped up to keep it around. Maintaining it is fairly complex, and I |
11 |
suspect the people most interested in the nuts and bolts of python are |
12 |
also the ones who are less interested in 2.7. I think most who want |
13 |
it to stay are more interested in it from the standpoint of keeping |
14 |
other software running, but may not be interested in actually taking |
15 |
care of 2.7 itself. |
16 |
|
17 |
These sorts of situations usually cause controversy. Sometimes |
18 |
somebody cares enough to maintain the software. Sometimes it happens |
19 |
in an overlay (which allows a maintainer to be a non-dev more easily, |
20 |
and it also eliminates most QA requirements so that can ease the |
21 |
burden of maintenance, though with the caveat that those QA standards |
22 |
exist for a reason so there are downsides). |
23 |
|
24 |
In the past when stuff like this has happened the software has |
25 |
generally ended up being taken out of the tree, because the fact is |
26 |
that stuff like this can break pretty quickly if nobody is fixing |
27 |
bugs, and if nobody wants to maintain it then that will be what |
28 |
happens. But, it is entirely possible that somebody will step up to |
29 |
maintain it. |
30 |
|
31 |
Python is a bit messier than some previous cases like this because of |
32 |
the whole way that PYTHON_TARGETS and such work, and the complexity of |
33 |
the dependency graph. And keep in mind that the upstream announced |
34 |
EOL is less than a month off. Not that this means the code instantly |
35 |
stops working, but that is why we're starting to see masks and such |
36 |
and more discussion/planning. |
37 |
|
38 |
-- |
39 |
Rich |