On 1/12/23 17:24, Glen Barney wrote:
On Wednesday, January 11, 2023 10:49 PM, Andrei Borzenkov wrote:
Sorry? The whole point is to have both versions at the same time.
Correct. I'm sorry that I failed to make that more clear. We need - and I would argue many developers working on Python would need - 3.9 and 3.10 (and future versions) installed side-by-side, same server, same time.
Interestingly that IS the case for python 2.7 and python 3.6. I have a machine with 2.7, 3.6, and 3.9 all installed together. So I cannot see any reason why 3.10 should not also work.
Most developers are using openSUSE Tumbleweed where Python 3.8, 3.9 and 3.10 are all co install-able and there is a different mechanism to set the default python and handle migrations. This was done post the release of Leap 15, so it was never implemented there and 3.6 will remain the default because that is what we promised SUSE customers. I expect that ALP will have a similar setup to tumbleweed and handling multiple python versions will be easier.
Sorry, but it does not explain *why* python39 must be removed and what prevents both versions to coexist. Sounds like a pure management decision.
Apologies if I am treading in areas I should not, but this does make me wonder: If this is in fact a management decision, is it possible to reach those managers and ask them to reconsider/change this?
Python 3.9 and 3.10 have never been officially supported in Leap 15.4 (I believe there are plans to have atleast one for 15.5) so if this was done to make package hub work properly for SUSE it will be hard to convince them to change it again. On the other hand branching the package and removing the conflicts and building a version for yourself is not hard. I can probably help walk you through the process a little later. -- 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