Ned Batchelder
Ned Batchelder
@adriangb can you say more about why you are pointing to that? Is it for me or the maintainers?
@hugovk Thanks for the heads-up, but this is a small enough change to accommodate later no matter what.
Can you say more about why you are running pytest 130 times? Why not run all the tests in one pytest run?
If you get one file per process, surely it's not the files that are the bottleneck? How are you determining what is the slow-down? Or is the problem something other...
I don't understand why pytest-cov isn't combining the files, but you can use `coverage combine` to do it.
I don't know if the intermediate files have been combined but not deleted, or if they haven't been combined. Does `coverage combine` work for you?
I'm sorry, I don't know the internals of pytest-cov well, so I don't know why they might not be combined. You could try setting COVERAGE_DEBUG=dataio and COVERAGE_DEBUG_FILE=/tmp/debug.out. Then you'll get...
This is a limitation of Python's: it optimizes away jumps to jumps, and you cannot disable the optimization.
If you are going to have a separate file for each tool, then explain why .coveragerc isn't good? What's wrong with the .ini format for coverage's settings? You can put...
We'll keep an eye on it and see if other tools start adopting a tool-specific.toml file pattern.