| 1 |
n952162 wrote: |
| 2 |
> On 11/15/20 2:53 PM, Alessandro Barbieri wrote: |
| 3 |
>> You are 5 years late |
| 4 |
>> |
| 5 |
>> >So, in 2008, we announced that we >would sunset Python 2 in 2015, |
| 6 |
>> and >asked people to upgrade before then. >Some did, but many did |
| 7 |
>> not. So, in 2014, >we extended that sunset till 2020. |
| 8 |
>> |
| 9 |
>> See also |
| 10 |
>> https://www.python.org/doc/sunset-python-2/ |
| 11 |
>> https://www.python.org/dev/peps/pep-0373/ |
| 12 |
>> https://pythonclock.org/ |
| 13 |
>> |
| 14 |
>> Il Dom 15 Nov 2020, 14:39 n952162 <n952162@×××.de |
| 15 |
>> <mailto:n952162@×××.de>> ha scritto: |
| 16 |
>> |
| 17 |
>> Suddenly, there's no python2 on my system, anywhere. Is that |
| 18 |
>> intentional? |
| 19 |
>> |
| 20 |
>> |
| 21 |
>> |
| 22 |
> |
| 23 |
> "Python 2.7 will not be maintained past 2020 |
| 24 |
> <https://www.python.org/dev/peps/pep-0373/>." |
| 25 |
> |
| 26 |
> There are no unmaintained packages in gentoo? |
| 27 |
> |
| 28 |
> |
| 29 |
|
| 30 |
|
| 31 |
|
| 32 |
Eventually unmaintained packages get treecleaned. If a package fails to |
| 33 |
build and someone files a bug report, that can easily trigger the |
| 34 |
treecleaning. Of course, there are systems that test these sorts of |
| 35 |
things and sometimes it catches packages that fail to build with the |
| 36 |
same result. They got names for those systems but I can't recall them. |
| 37 |
From my understanding, they build various packages and look for build |
| 38 |
failures and report problems. |
| 39 |
|
| 40 |
So, while there may be a few that have no maintainer but still work, |
| 41 |
there is likely very, very few that have no maintainer and fail to |
| 42 |
build. I monitor -dev and I see last rites for packages all the time |
| 43 |
for just that reason. On occasion someone picks up a package and fixes |
| 44 |
them but quite often, the package is dead upstream and been replaced by |
| 45 |
something newer, just like python 2.7 is doing. It's just that python |
| 46 |
is going to newer versions that aren't compatible with the old ways. |
| 47 |
|
| 48 |
I've seen so many posts about python 2.7 going away, I'm pretty glad it |
| 49 |
is gone. The devs have been posting and working on this for a long, |
| 50 |
long time now. I might add, it took quite a lot of effort on their part |
| 51 |
as well. |
| 52 |
|
| 53 |
Dale |
| 54 |
|
| 55 |
:-) :-) |
Archives