Bugzilla – Bug 1216195
obs: cannot use macro %pyproject_wheel for building python packages for leap 15.5
Last modified: 2023-10-26 06:38:01 UTC
I have a python package that is build on obs. Such packages used to support python 3.6 and was simple to build for tumbleweed and leap. Recently support for python 3.6 was dropped by such package. The solution was to use the macro sle15_python_module_pythons to build such packages on tumbleweed and Leap using a modern python. However, this works as long as I use the legacy macro %python_build and %python_install. All is required is to use (for leap 15.5): Buildrequires: python311-devel Buildrequires: python311-setuptools Now the package I want to build has migrated to the modern PEP517/PEP518 way. It means I need to use the macro: %pyproject_wheel and %pyproject_install and, for them to work on leap 15.5, I need to use: Buildrequires: python311-pip Buildrequires: python311-wheel The issue is that python311-wheel is not available for Leap 15.5 and therefore the macro %pyproject_wheel fails to run. I'm wondering if the missing rpm python311-wheel from Leap 15.5 is a bug or am I doing something wrong? I could not find anything on https://en.opensuse.org/openSUSE:Packaging_Python that can help me use %pyproject_wheel to build a package on Leap 15.5.
This is currently not a bug. Leap 15.5 only provides setuptools and pip and Python 3.11 itself to install packages from PyPi, not to build other packages against Python 3.11. Sorry.
In June there was this announcement: https://news.opensuse.org/2023/06/06/leap-modern-python-stack/ about the python 3.11 stack for leap. That would solve my problem. The question is: is it ever going to happen?
(In reply to Giacomo Comes from comment #2) > In June there was this announcement: > https://news.opensuse.org/2023/06/06/leap-modern-python-stack/ > about the python 3.11 stack for leap. > That would solve my problem. The question is: is it ever going to happen? It's on its way, I think that it'll happen during November, it's a big maintenance update happening in SLES SP4 and it's going through all the QA, so it's taking more time than expected, but if everything goes correctly it should be available in leap soon.
> It's on its way, I think that it'll happen during November, it's a big > maintenance update happening in SLES SP4 and it's going through all the QA, > so it's taking more time than expected, but if everything goes correctly it > should be available in leap soon. the python3.11 stack landed today in Leap 15.4 and 15.5. It consists of about 260 source packages, which is good. However the announce was mentioning 500 packages. Are more python311 packages going to be added in the future? I'm asking because the python package I maintain needs at runtime python-gobject and python-pycairo and I was wondering if they too will be available in the future.
(In reply to Giacomo Comes from comment #4) > > It's on its way, I think that it'll happen during November, it's a big > > maintenance update happening in SLES SP4 and it's going through all the QA, > > so it's taking more time than expected, but if everything goes correctly it > > should be available in leap soon. > > the python3.11 stack landed today in Leap 15.4 and 15.5. It consists of > about 260 source packages, which is good. However the announce was > mentioning 500 packages. Are more python311 packages going to be added in > the future? > I'm asking because the python package I maintain needs at runtime > python-gobject and python-pycairo and I was wondering if they too will be > available in the future. Yes, there's another batch in review right now with 134 more packages and python-gobject and python-pycairo packages are there.