On mié, 2023-04-26 at 17:50 +0200, aplanas wrote:
On 2023-04-26 17:34, Daniel Garcia wrote:
Our test project has this macro:
%sle15_python_module_pythons() %global pythons python311
The idea is to provide a modern version of a reduced list of python packages and build this list with python 3.11.
Sorry if a join late and misinformed. I saw the PRs of this macro and I think that now I grasp the goal. IIUC the same python module (same version, same source code) will be compiled for 36 and 311 if this macro is present, making is a kind of a marker or flag.
If this is correct, I wonder if polluting hundreds of Factory packages with this macro (that is nil for Tumbleweed) was the correct technical approach, and that the same goal could be achieved via some OBS/IBS work, where a subproject links the same list of packages (but with a project config that set the python to 3.11), and a later _aggregate somehow collect them into the main distribution.
This is nil for Tumbleweed, but will be useful in Leap, when building packages for a modern python version, the same way we're trying to do in SLE15-SP4. The main reason we submitted this to factory (other than "factory first policy") is that we've the project devel:languages:python:backports and we would like to make that project more useful than it is today. It currently has thousands of unresolvables with no chance of making it green as almost everything has dropped 3.6 support. Regards. -- Daniel García Moreno Python Packager