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
Given that we have control over how and where source files get used by the
virtualenv, your suggestion seems within reach by doing a bit of
temporary-directory dancing. I've been hitting some issues with that
(unrelated to Cython as far as I can tell), and will attempt to update this
thread after d
Masood Malekghassemi via cython-devel schrieb am 08.10.2015 um 01:06:
> 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 project than the
> one which contains the Cython f
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
