Relevant reads: https://docs.pytest.org/en/latest/explanation/goodpractices.html#choosing-a-... https://docs.pytest.org/en/latest/explanation/pythonpath.html
the tests will run against the installed version of pkg_under_test when --import-mode=append is used whereas with prepend they would pick up the local version.
Am 24.05.21 um 09:42 schrieb pgajdos:
See home:pgajdos:python/python-bitstruct
What is preferred solution for the spec file?
Why use pytest at all? The recommended way to replace `python setup.py test` is to call `python -m unittest` directly. If it is supported by all build targets (you need to adjust your Leap 15.2 target to include backports), you can use the macro: mv bitstruct bitstruct.mv %pyunittest_arch discover -v tests - Ben