-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
WinAmp 2 (1998) was widely liked. WinAmp 3 (2002) was considered bloated, and flopped.
So Nullsoft followed it up with WinAmp 5 – because 2+3=5 – in 2003, which was very broadly the codebase of WinAmp 2 (small and lean) plus the skin support from WinAmp 3 (the only part people liked).
This won people back, and WinAmp is still around and got an update this year, 20 years on.
I think it's too late for there to be a Python 5, but I did read a blog post long ago – which I can't find again, or I'd link to it – which proposed a similar compromise fix to Python, in considerable technical detail.
I am with @blagie on this: the Python world handled the 2→3 transition spectacularly badly. V3 didn't deliver enough, and strong-arming people by just end-of-lifing Python 2 and expecting the world to move on was foolhardy and short-sighted.
(And I don't even use the language myself. I'm just observing.)
It's a real shame Tauthon didn't get more traction and support.
https://github.com/naftaliharris/tauthon
If it had got enough support and continued, maybe the Python maintainers would have learned something, but I've not seen any sign that they have.
This is nothing new. For comparison, Perl 6 went so badly that Perl 5 now looks likely to continue as Perl 7:
https://www.perl.com/article/announcing-perl-7/
And PHP 6 didn't really happen -- AFAICT as a total outsider, Unicode support proved too hard and it was never released; the community backported the important bits to PHP 5, and then a new PHP 7, more modest in scope, developed from PHP 5.
The Python world could have done the same, and Tauthon was an effort in that direction.
It's too late now. I suspect that, just as Perl has lost a massive amount of interest and use, partly from the nearly-two-decade-long effort to release Perl 5, Python has done the same -- sabotaged its own community with this high-handed "your leaders know best" approach.
Kpatch is fully open
https://github.com/dynup/kpatch
But if you mean the Kernel patch packages themselves, then you are right, looks like there are no free patch packages that one can just download and use.