On Mon, Jan 3, 2022 at 8:48 AM Simon Lees <sflees@suse.de> wrote:
On 1/3/22 21:38, Michael Ströder wrote:
On 1/3/22 10:45, Ben Greiner wrote:
Am 03.01.22 um 09:52 schrieb Michael Ströder:
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.
Before this thread develops into the 10th or so discussion about Python versions in Leap and Tumbleweed within the last 12 moths: Please be very specific about your demands and claims. The "instead of a newer version" will immediately be dismissed by the fact that 15.3 already ships the Python 3.9 interpreter in addition to 3.6 and there was once an announcement here on the list that they even want to include Python 3.10 in 15.4.
IMO the fact that standard /usr/bin/python3 is not maintained upstream anymore is enough to rule out Python 3.6 in Leap 15.4. The non-standard interpreters 3.9+ are mainly only usable for developing software in virtual envs.
The real discussion is about what Python version the system packages have to use.
Yes.
In my case e.g. aehostd is system software. Now try to explain to an auditor that this security relevant system software runs on a unmaintained Python version. Yeah, have fun.
This is simple, the python 3.6 is still maintained just by a different group of people, if significant python 3.6 security issues are found they will be fixed by someone within SUSE, this is a guarantee we give to our customers
And because, as I understand it, all 15.X releases need to maintain the binary compatibility of earlier 15 releases, they cannot move away from Python 3.6.
And this is set in stone forever?
Forever being atleast the 15.X series where we have promised customers we won't break binary compatibility or remove functionality. Maybe in future SLE versions the model will be different but I am as yet unsure.
Insisting on using this ancient stuff makes openSUSE *and* SLE look really bad compared to other distros and will cause nothing than grief.
I tend to agree with this, although in my eyes the solution is having SLE / Leap 16 available sooner although lots of people might disagree with me for lots of reasons.
I'd really like to see SLE/Leap 16 sooner rather than later too. The tech debt in SLE 15 is piling up and a lot of stuff that I've done in Tumbleweed for that future SLE version can't be backported because they're foundational things that would make SLE 15 into a different SLE anyway. -- 真実はいつも一つ！/ Always, there's only one truth!