Dne 03. 01. 22 v 10:45 Ben Greiner napsal(a):
It's the decision of SUSE and they have to allocate the manpower to support their Enterprise products. I am not sure if the decision makers are really aware of the consequences. As evidenced how the python36 drop in Tumbleweed and the python310 introductions are handled, and the by the increasing number of threads popping up on the mailing lists, reddit posts and so on about Python versions, there is at least a lack of clear communication to the community about it.
1. We are seriously aware how poorly we communicate our policy decisions about Python, so any specific suggestion what's missing (or any volunteering work on the improvements) are more than welcome. 2. I can assure you that too-slow/too-fast problem is something we are acutely aware of, it is probably one of the biggest problems all Linux distributors are struggling with, but nobody came with really good solution. With every user who is angry with us for moving too fast and upgrading too much, there is at least one user or more who is angry with us for moving too slow and not upgrading enough. Currently, the leading solution seem to lead to heavy use of containers, but then there are already users of containers who are becoming quite aware of problems with maintaining content of those containers, and the circle just continues. 3. The fact of life (and I am not much happy with it personally) is that Python 3 in SLE-15 will be 3.6 (and with the EOL, 3.6.15 now forever). Period. Currently, the policy is that every new service pack of SLE-15 will have also the “latest” interpreter-only Python (3.10 for SP4), which will replace the previous latest version. Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Only those laugh of wounds, who never have been hurt. -- despair.com