On 1/3/22 21:47, Michael Ströder wrote:
On 1/3/22 11:22, Simon Lees wrote:
On 1/3/22 19:22, Michael Ströder wrote:
Python 3.6 has reached EOL and various Python module packages already drop support for 3.6. But still Python 3.6 is planned to be shipped with Leap 15.4 instead of a newer version.
Instead of should read as "As well as"
IMO this does not make sense at all.
This is what SUSE's customers want so SUSE pays people to maintain certain versions of python even after upstream doesn't. Its also why they paid people to develop "Single Spec" to make it easier to maintain multiple versions of python packages in Leap.
In know this theoretical argument quite well. But I'm really tired of it.
Outdated is not "stable".
I have some customers running SLE and in practice 3rd-party Python packages are not well-maintained and are too old for installing recent software. So in real life this causes all sorts of additional efforts, even with really bad work-arounds. IMO it's a bad product management decision.
I am not a product manager so I don't get to make such decisions and can't really speak on behalf of them, but what I can say is the general use case that is put to us is we have customers who for example buy a new piece of hardware, provision it with the services they require and then expect not to need to touch that system again for the 5 year lifetime of the hardware other then for security updates. Then in 5 years when the hardware is end of life before decommissioning it they will set up new hardware with an updated software stack and use that for the next 5 years. This is one of the main usecases SLE has to support and unfortunately because openSUSE on its own doesn't have the man power to do something else it chooses to inherit SLE for Leap and therefore Leap has to be able to live with similar constraints. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B