Overview
Request 1218423 accepted
Enable sle15_python_module_pythons.
- Created by esampson
- In state accepted
-
Package maintainer:
bruno_friedmann
Loading...
openSUSE Build Service is sponsored by
Enable sle15_python_module_pythons.
bruno_friedmann
What this macro is suppose to do ? rpm --eval %sle15_python_module_pythons %sle15_python_module_pythons Why sle15 when we go for 16 ?
it causes the rpms to get created as: python3xx- on the current 310-312, without it rpms only created as python3- see: https://build.opensuse.org/projects/home:yeey:OpenWebUI/packages/python-aiohttp/repositories/openSUSE_Tumbleweed/binaries
It's for the Leap. It builds the package with the more modern Python 3.11 interpreter instead of the native Python 3.6.
You should never add something that is redondant, we have since years multiple python target working in Factory/TW S | Name | Type | Version | Arch | Repository ---+----------------------+---------+-----------+--------+----------- | python310-et_xmlfile | package | 1.0.1-4.8 | noarch | oss i+ | python311-et_xmlfile | package | 1.0.1-4.8 | noarch | oss | python312-et_xmlfile | package | 1.0.1-4.8 | noarch | oss
So there's no need to add another macros.
With all due respect, sir, I am the lead package of Python for SUSE and I have to say that you don’t know what you are talking about. The situation on SLE (and thus Leap) is by far more complex than you can imagine. I spent a year or so of my life preparing a special Python 3.11 module for SLE-15, and we will have fun of maintaining it probably until I retire (somewhere around 2037). It is really a bit more complicated than with TW. This macro is the officially sanctioned way how to make modern packaged
python311-*package for SLE/Leap.Hi Matej, no offenses, I know who and what you're doing, I was super surprise you didn't go for a simpler solution like in TW for Leap and that I didn't find active the macro on my TW (due to the factory first rule), but that's certainly a piece of the puzzle I'm not aware off. Have fun with 16