Daniel Hahler
Daniel Hahler
You can use `export COVERAGE_DEBUG=process,config,dataio` (or similar, see coverage.py docs) to debug this (look at "config_files", cwds etc).
Related https://github.com/pytest-dev/pytest/issues/759 (search for idsetfn), and some (stalled) WIP: https://github.com/blueyed/pytest/pull/104
Yes, controlling this in another way sounds useful. One solution for this might be to skip the warning during import of the (entrypoint) plugin (and also for `-p coverage.pytest_plugin`), only...
At least all existing tests are passing.. ;) \o/
Thanks! I came across that before, but for `zsh` it requires `bashcompinit` (a wrapper to enable bash completions), and the completion itself is slow (it seems to be not cached...
> But it doesn't seem necessary to actually remove the option, does it? Or is just a matter to cleanup what we believe is mostly an unused option? Yes, for...
I think we do not have to dump/remove the option, only because our own tests fail with it.
@adamchainz There are CI failures.. do you have an update?
It should likely use some more specific pytest hook, e.g. `pytest_configure`. In general I think that running this separately in CI is better than with (possibly) every pytest invocation.
Ok. I'm ok with adding it, but there should be an option for it, defaulting to off in my opinion - but I would be happy enough if I could...