On 1/3/22 21:11, Ben Greiner wrote:
Am 03.01.22 um 11:22 schrieb Simon Lees:
On 1/3/22 19:22, Michael Ströder wrote:
HI!
Python 3.6 has reached EOL and various Python module packages already drop support for 3.6. (...)
(...) Its also why they paid people to develop "Single Spec" to make it easier to maintain multiple versions of python packages in Leap.
A note of caution: The singlespec approach only works when a package supports all target flavors. Lots of upstream packages only introduced compatibility with Python 3.9 or Python 3.10 after they dropped Python 3.6 support. So when you plan to enable a python39 or python310 flavor in 15.4, and that is how I read your statement, you will still require a paid SUSE engineer to either maintain two different package versions or that lots of suse-specific patches need to be introduced. With the Factory first approach, these patches would also appear in Tumbleweed, making the life harder for everyone.
That's not quite how the factory first approach works, factory first is about making sure that bugfixes and features that go into SLE releases also go into tumbleweed so that they make it into the next major SLE release. Given that python 3.6 will soon be dropped from tumbleweed and won't be in SLE-16 patches related to keeping python 3.6 don't need to go into factory, in the same way sometimes in SLE / Leap we use a patch to fix an issue rather then taking a newer version and we don't send that patch to factory if we take the newer version there. What matters in factory first is the issue is resolved in both SLE and Factory so in this case it shouldn't affect tumbleweed, and yes if customers need the package for both then we will work on it because that is why they pay us. -- 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