Test coverage reporting not working properly with pure Python builds, since line tracing in inclusion in reports just happens for native .pyx files.
An alternative workflow would be:
delete compiled module from source tree (is imported used for tests if present)
run tests (now the plain Python module is used and coverage reporting works as expected)
install package with pdm install into environment (builds extension module via Cython)
run tests again (only for the relevant modules) and see if they pass (now the compiled module is used; since it is just the translated version of the pure Python module you can assume that everything works as expected and that the test coverage is equivalent to the pure Python file)
Test coverage reporting not working properly with pure Python builds, since line tracing in inclusion in reports just happens for native `.pyx` files.
An alternative workflow would be:
- delete compiled module from source tree (is imported used for tests if present)
- run tests (now the plain Python module is used and coverage reporting works as expected)
- install package with `pdm install` into environment (builds extension module via Cython)
- run tests again (only for the relevant modules) and see if they pass (now the compiled module is used; since it is just the translated version of the pure Python module you can assume that everything works as expected and that the test coverage is equivalent to the pure Python file)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Test coverage reporting not working properly with pure Python builds, since line tracing in inclusion in reports just happens for native
.pyxfiles.An alternative workflow would be:
pdm installinto environment (builds extension module via Cython)