Ned Batchelder

I like the idea of a new setting indicating lines that are expected to be unexecuted, and will warn if they are executed. Like `exclude_lines`, it would be a regex...

Another option: `warn_if_run_lines`, which is more direct. Also, I'm wondering about which command should issue the warning. `coverage report` is a natural choice, but there are other reporting commands that...

Thinking about how to do this some more... First, I wish there were a good word to mean, "lines I thought wouldn't execute, but did," like we have "unexecuted" for...

This would be a change in how the command line arguments are used. Can you tell me more about how PyCharm is setting the omit option, and how you are...

Creating a .coveragerc file like this makes everything measured correctly: ``` [run] concurrency = multiprocessing parallel = true ``` Then use `coverage combine` to combine the data, and the report...

Hi, sorry to let this sit. What plugin behavior in particular are you looking for? The key idea of sys.monitoring that makes it fast is to disable an event once...

@markshannon any clues what this means here?

That does indeed seem wrong. But tell me more about the pragma on line 8... if you don't expect line 8 to run, then how would line 10 run? Can...

I have no objections to those changes, I just don't feel much need to make them. I don't use pre-commit hooks, but if we add the ruff checks to CI...

Try adding this setting to your .coveragerc file (or other setting file): [relative_files](https://coverage.readthedocs.io/en/7.2.5/config.html#run-relative-files): ``` [run] relative_files = true ```