Am 13.07.22 um 16:38 schrieb Michael Ströder:
On 7/13/22 16:22, Simon Lees wrote:
The complicated part and likely the reason for looking for additional maintainers is dealing with all the libraries that once had a version that worked with 3.6 which would currently ship with Leap but the newer version doesn't work with 3.6 but does work with 3.10 in this case there will be extra packages to maintain because single spec can't be used, this might also cause other dependency issues that require a newer version for 3.10 then 3.6 and as such not being able to use single spec.
Yes, especially since the number of modules for which upstream drops Python 3.6 is growing very fast. It expect this to be a real mess.
Sorry, I have to repeat myself: Shipping unmaintained Python version is wrong.
Ciao, Michael.
Call me naive, but I don't see the problem. The python 3.6 and python 3.10 world are separate enough for our purposes. All existing SLE/Leap packages work with Python 3.6 and are able to do so, because nothing gets removed. Everything which needs an update will migrate to the python 3.10 namespace and ignore all that is in the python 3.6 namespace. We have a great deal of experience in Tumbleweed with co-installable python flavors. Now is the time to reap the benefits for Leap.