Eric Schirra wrote:
The second is that there are no python311 packages under Leap. So the whole thing cannot work at all.
They're in progress of being added to Leap, however that comes via maintenance and will take time.
And all packages in Leap are called python- and not python3-.
And that's okay. you can keep it that way *unless* you want to update to 3.11. The rename to python3 is only needed if you have two different source versions (one for 3.6 and one for 3.11). if you can build for both or only build for python3 no work is needed.
Why is not simply the old 3.6 left and only additionally added e.g. 3.11?
Thats what we're doing
As it practically Tumblweeed also does?
Because Tumbleweed and Leap are different release models, we need to cater both.
And then all existing python packages also built for python 311. Additionally. Then everyone can take the version he wants and he could possibly switch all his packages to 311. If he wants.
That is the plan. Just that practically there is less than 0.5% of packages that build with the same source for python 3.6 and python 3.11 at the same time, the "tumbleweed model" does not work for Leap.
Since phython311 packages bring me nothing at all, because there is no python311 and secondly all other python packages that I need for my package are 3.6 packages.
then build for 3.6. Greetings, Dirk