Hi Daniel, thanks for the reply. On 26.04.23 at 17:51 Daniel Garcia wrote:
On mié, 2023-04-26 at 13:34 +0200, Johannes Kastl wrote:
(I am asking because I needed to jump through quite some hoops to build ansible for SLES15 with python3.10 from the Python3 module. If this macro makes it easier to do so I would be interested...)
Possibly it will make it easier, but for python 3.11.
I'll take what is avaiable in the Python3 module. :-)
We're building a reduced list of basic python packages, the modern version, just directly from Tumbleweed, to provide it in SLE15-SP4, so it should be available, but just in the python module.
Here you can find the devel project that we're using to build the list of packages and fix issues: https://build.opensuse.org/project/show/home:dirkmueller:acdc:as_python3_mod...
I've just updated the initial doc in the wiki, added by Robert, with a more detailed explanation: https://en.opensuse.org/openSUSE:Packaging_Python#Python_3_(Leap_Future)
1. Currently I set those lines in the prjconf in the SLES15+Python3 projects: ``` %define pythons python310 Macros: %pythons python310 :Macros ``` IIUC I can just remove this, once the macro was added to each package? 2. Currently I hardcode the versions for Tumbleweed and SLES15 in e.g. the ansible-core spec file: ``` %if 0%{?suse_version} < 1550 # Leap15, SLES15 %define pythons python310 %define ansible_python python310 %define ansible_python_executable python3.10 %define ansible_python_sitelib %python310_sitelib %else # Tumbleweed %define pythons python3 %define ansible_python python3 %define ansible_python_executable python3 %define ansible_python_sitelib %python3_sitelib %endif ``` I assume that this needs to be adapted to 3.11 (and possibly other versions in the future?)? Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537