Ned Batchelder
Ned Batchelder
@webknjaz @OlenaYefymenko What is left to do with this PR?
Thanks for doing this, and thanks for persisting. With these changes, the `.coverage.toml` file would have entries like: ```toml [tool.coverage.run] branch = true ``` but wouldn't we want this?: ```toml...
I hope this doesn't seem like a cop-out: I think there are good arguments for both side, and I'd like to support both prefixed and un-prefixed settings, aiming for the...
I appreciate the thought and effort you are putting into this. Four tabs sounds reasonable. I'd prefer this order, and I've snuck in a comment to help people understand the...
>> BTW, I hadn't really noticed until now, but this PR names the file .coveragerc.toml, when it should be .coverage.toml. > > I requested that name originally since it sounded...
> I'm not sure I agree that `.coverage.toml` (config file) would be confused for `.coverage` (results DB). The problem isn't that people will confuse the two. The default database name...
I'm sorry I never responded to this! @zackw You should be able to simplify your `[paths]` as @marcelotduarte shows by using wildcards to abstract away parts of the paths. But...
I'm disappointed that this hasn't even been discussed on this issue. I love that you are taking security seriously by preventing accidental upload of sensitive data. But it's really disappointing...
Hmm, this has been a bug for a long time. In 6.0.0 (Oct '21) through 6.4.1 (June '22), the message was "didn't jump to line 0". In 6.4.2 (July '22),...
This is fixed in commit c85eaba206e1bf98302e0997e32c079e2c231f4b.