openSUSE Python

Download

python@lists.opensuse.org

August 2023

3 participants
12 discussions

Re: Python testsuite won't find module despite package in BuildRequires
by Ben Greiner 01 Aug '23

01 Aug '23

Hi Adrian, Am 24.03.23 um 14:15 schrieb Adrian Glaubitz via openSUSE Factory: > Hi! > > The Python package python-azure-devops has been failing to build in Factory for > some time and the necessary fixes have so far been fixed in upstream git only > but without any new release. > > I have therefore decided to package a current git snapshot to fix the build problem > with the package. However, there is now an issue with the testsuite that I have not > been able to sort out [1]: > > [ 16s] ====================================================================== > [ 16s] ERROR: azure.devops.v6_0.work_item_tracking_process_template (unittest.loader._FailedTest) > [ 16s] ---------------------------------------------------------------------- > [ 16s] ImportError: Failed to import test module: azure.devops.v6_0.work_item_tracking_process_template > [ 16s] Traceback (most recent call last): > [ 16s] File "/usr/lib64/python3.8/unittest/loader.py", line 470, in _find_test_path > [ 16s] package = self._get_module_from_name(name) > [ 16s] File "/usr/lib64/python3.8/unittest/loader.py", line 377, in _get_module_from_name > [ 16s] __import__(name) > [ 16s] File "/home/abuild/rpmbuild/BUILD/azure-devops-7.0.0/azure/devops/v6_0/work_item_tracking_process_template/__init__.py", line 9, in <module> > [ 16s] from .models import * > [ 16s] File "/home/abuild/rpmbuild/BUILD/azure-devops-7.0.0/azure/devops/v6_0/work_item_tracking_process_template/models.py", line 9, in <module> > [ 16s] from msrest.serialization import Model > [ 16s] File "/usr/lib/python3.8/site-packages/msrest/__init__.py", line 28, in <module> > [ 16s] from .configuration import Configuration > [ 16s] File "/usr/lib/python3.8/site-packages/msrest/configuration.py", line 38, in <module> > [ 16s] from .universal_http.requests import ( > [ 16s] File "/usr/lib/python3.8/site-packages/msrest/universal_http/__init__.py", line 53, in <module> > [ 16s] from ..exceptions import ClientRequestError, raise_with_traceback > [ 16s] File "/usr/lib/python3.8/site-packages/msrest/exceptions.py", line 31, in <module> > [ 16s] from azure.core.exceptions import SerializationError, DeserializationError > [ 16s] ModuleNotFoundError: No module named 'azure.core' > > During the testsuite run, the Python interpreter complains that it cannot import > azure.core despite python-azure-core being installed through BuildRequires. > > When I change into the build root with "osc chroot", I can actually import "azure.core" > from an interactive Python instance after running "python38", for example. However, > once I have made a testsuite test run with "python38 setup.py test", this no longer > works and I am getting the error that is shown during the testsuite run. - There is no python38 command. You probably mean python3.8? setup.py test has been deprecated a long time ago. Use unittest or pytest, we have macros for it. Upstream uses pytest [2] although the single test file [3] is written to work with plain unittest. > > I have tried setting PYTHONPATH, but that didn't help. > > Does anyone have a suggestion? I have currently disabled the testsuite in my home project, > but I actually want to submit the package with the testsuite remaining enabled. Requires: python-azure-nspkg >= 3.0.0 ... rm -rf %{buildroot}%{$python_sitelib}/azure/__init__.* Did you check if this ist still the correct setup? There is a bunch of namespace techniques in Python which contradict each other when mixed. If the nspkg is still the desired and consistent setup, you probably have to keep the __init__.py in the BUILDROOT for the testsuite and only %exclude the file in the %files section instead of deleting it too early. > > Thanks, > Adrian > >> [1] https://build.opensuse.org/package/show/home:glaubitz:branches:devel:langua… - Ben [2] https://github.com/microsoft/azure-devops-python-api/blob/dev/.github/workf… [3] https://github.com/microsoft/azure-devops-python-api/blob/dev/azure-devops/…

3 3

Building singlespec for only the default python on Tumbleweed (and SLES15/Leap15)?
by Johannes Kastl 01 Aug '23

01 Aug '23

Hi all, I finally have all the bits and pieces to get nitropy aka pynitrokey into Tumbleweed. The package itself is building and working, but I would like to polish it up a little. One thing I might have overlooked in the Python-Packaging documentation is how to build for only the default python on Tumbleweed. I currently have this in the spec: %{?sle15_python_module_pythons} %define skip_python38 1 %define skip_python39 1 %define skip_python310 1 %define skip_python312 1 This will build it for python3.11 now on Tumbleweed and SLES15 (if the dependencies are there). But it will break once Tumbleweed switches to 3.12. Is there a nice little macro to achieve that? The %primary_python macro is not set by the sles15 macro, AFAICT. If there is no other way, I'll use a "0%{?suse_version} < 1699" thingy to target SLES15. But if there is a nicer way I would like to use that... Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)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

3 3