Tests do not run in PEP517 out-of-source build (gentoo) about bx-python HOT 5 OPEN

I could get most tests to run by linking pytest.ini and test_data into the built directory and calling pytest from there.

That's good progress, thanks for your work on that!

Now, only the following two fail:

lib.linux-x86_64-cpython-312/bx/binned_array_tests.py::test_file_lzo
lib.linux-x86_64-cpython-312/bx/binned_array_tests.py::test_binned_array_writer

both with:

compress = comp_types[comp_type][0]
E       KeyError: 'lzo'

That's likely due to missing python-lzo, which is not strictly required by bx-python but it's need for these tests to pass, see https://github.com/bxlab/bx-python/blob/main/tox.ini#L16

from bx-python.

Thanks for reporting the issue!
@mr-c Maybe you have suggestions from the Debian packaging?

from bx-python.

The issue here seems to be that -m gpep517 (at least in Gentoo ebuilds) does not allow in-source builds. The pytest.ini and test_data are in the sources, while the compiled (or installed) package is in a separate directory.

I could get most tests to run by linking pytest.ini and test_data into the built directory and calling pytest from there.

Now, only the following two fail:

lib.linux-x86_64-cpython-312/bx/binned_array_tests.py::test_file_lzo
lib.linux-x86_64-cpython-312/bx/binned_array_tests.py::test_binned_array_writer

both with:

compress = comp_types[comp_type][0]
E       KeyError: 'lzo'

from bx-python.

Oh yes, that makes sense. Thank you!

I edited the title for the PEP517 tests, please feel free to leave open or close as you prefer.

from bx-python.

@mschubert Sorry for late reply here, if there's anything that we can do here that would make your life easier let us know!

from bx-python.