Hi Eric, On sáb, 2023-05-06 at 11:27 +0200, Eric Schirra wrote:
Now it's me again. Sorry if it is annoying.
Using the GUI of the web browser I can't find an entry in ProjectConfig with %sle15_python_module_pythons().
But if I use "osc buildconfig home:ecsos 15.4" to display the ProjectConfig there appears:
#request by slemke/dmueller 2023-05-04 for python311 builds. macros: # Macro to build Python stack proposal packages %sle15_python_module_pythons() %global pythons python311 :macros
Why is that in there? According to your previous explanation, this is also observed in the specs and thus python311 is built. (But also only 311. Nothing else) Surely this should not be? Or is that now nevertheless firmly everywhere in it? Does he think that is a mistake? Why? How do I get the way? I do not see him online. Or can you take care of it and correct it?
The macro is now defined in the SUSE:SLE-15-SP4:Update project, so any project that derives from that will have the macro defined. The idea of that macro is to use it to build a reduced list of python packages for a modern python version (python 3.11), but the default Python (%primary_python) will continue to be the same, python 3.6. We will rename the source packages to build the Python 3.6 package version, so packages with name python3-foo will produce python3-foo.rpm binaries and packages with name python-foo will produce python311-foo.rpm. The second ones are the only that will have the new macro, the python3-foo kind of packages shouldn't have the new macro because they will continue using the default python defined in the project. So to make it more clear, if a spec file have the sle15_python_module_pythons macro, it's because that package will be built with the modern python version (Python 3.11). The python311, python311-pip and python311-setuptools packages are going to land in SP4 (and therefore in SP5) soon, and when we've that, packages with the new macro will build correctly in different projects, like devel:languages:python:backports. Indeed, pip and setuptools will be built using the new macro. I hope that this explanation helps to understand better what we're trying to do and what's happening right now (we added the macro to be able to build packages, but packages are not there yet, under review). Regards -- Daniel García Moreno Python Packager