Am 2022-06-24 um 12:12 schrieb Richard Brown:
A more nuanced point of course would be to realise that, if ALP delivers on even a minority of it's stated goals, with everything containerised the problems Axel is finding with Leap would no longer apply, because people should be able to mix and match containers from various codestreams..
Yes, but ALP is not planned to be active in SLE/Leap 15, is it? But SLE/Leap 15 still has some time to go, and having e. g. an ancient python base does not help anyone. And as far as I understand this, Axel is considering SLE/Leap 15. * users of SLE 15 (and Leap 15) have to make sure that their locally needed python software is backwards compatible to the old base * maintainers of python packages have to care about the backwards compatibility as well when upstream moves on Wouldn't it be less work if python base was updated to a recent version, since the current versions of python software already support that version? The maintaners have less backporting work to do. Or, as I see with SLE 15.4, there is a Python3 module now parallel to the already existing Python2 module, and it contains a newer base, hooray! Werner --