n952162 wrote:
> On 11/15/20 2:53 PM, Alessandro Barbieri wrote:
>> You are 5 years late
>>
>> >So, in 2008, we announced that we >would sunset Python 2 in 2015,
>> and >asked people to upgrade before then. >Some did, but many did
>> not. So, in 2014, >we extended that sunset till 2020.
>>
>> See also
>> https://www.python.org/doc/sunset-python-2/
>> https://www.python.org/dev/peps/pep-0373/
>> https://pythonclock.org/
>>
>> Il Dom 15 Nov 2020, 14:39 n952162 <n952...@web.de
>> <mailto:n952...@web.de>> ha scritto:
>>
>>     Suddenly, there's no python2 on my system, anywhere.  Is that
>>     intentional?
>>
>>
>>
>
> "Python 2.7 will not be maintained past 2020
> <https://www.python.org/dev/peps/pep-0373/>."
>
> There are no unmaintained packages in gentoo?
>
>



Eventually unmaintained packages get treecleaned.  If a package fails to
build and someone files a bug report, that can easily trigger the
treecleaning.  Of course, there are systems that test these sorts of
things and sometimes it catches packages that fail to build with the
same result.  They got names for those systems but I can't recall them. 
>From my understanding, they build various packages and look for build
failures and report problems. 

So, while there may be a few that have no maintainer but still work,
there is likely very, very few that have no maintainer and fail to
build.  I monitor -dev and I see last rites for packages all the time
for just that reason. On occasion someone picks up a package and fixes
them but quite often, the package is dead upstream and been replaced by
something newer, just like python 2.7 is doing.  It's just that python
is going to newer versions that aren't compatible with the old ways. 

I've seen so many posts about python 2.7 going away, I'm pretty glad it
is gone.  The devs have been posting and working on this for a long,
long time now.  I might add, it took quite a lot of effort on their part
as well. 

Dale

:-)  :-) 

Reply via email to