I'd asked this of Robert Bradshaw earlier and was pointed in this direction
(specifically towards Stefan), so here goes!
I'm having trouble with getting Cython to play nicely with the coverage.py
tool via the Cython.Coverage plug-in.
We have tests that are running from a different setup.py projec
e
blessed example project demonstrating the basic coverage+testing setup
along the way for Cython, possibly with some glue to e.g. py.test or
nosetests or nose2 or even a custom distutils/setuptools test command etc..
Thanks for the response!
On Sat, Oct 10, 2015 at 8:27 AM, Stefan Behnel wrot
After reorganizing the code such that all the tests are located back in the
same project, setting up the running of tests in-tree, and using the
unittest module directly, there's been much success! Automatically suffixed
.coverage files are generated per test case and merged at the end (keeping
ope
tl;dr: How ought one fix file tracing paths for Cython coverage?
Hello y'all,
I'm currently trying to integrate C code into the GRPC Python project
wherein said code is outside of my control, and belonging to the umbrella
GRPC project. The Python+Cython code exists in a subdirectory (i.e. the
pac
