Ned Batchelder comments

Results 963 comments of


                                            Ned Batchelder

Assume `if TYPE_CHECKING: ... else: ...` block is covered

A few years later, I think you are right that it should be part of the default. If the user wants to measure those lines, they can.

Coverage >= 5 cannot handle Cython `public` or `readonly` members in `.pxd` file

Thanks, I see the error from "coverage report", but I don't see the message you show for "coverage run". Do you have any other context I need?

Coverage >= 5 cannot handle Cython `public` or `readonly` members in `.pxd` file

I got it from the "debug sys" output you showed: you have a .coveragerc file with this: ``` [coverage:run] # http://blog.behnel.de/posts/coverage-analysis-for-cython-modules.html plugins = Cython.Coverage ``` Now I see the same...

Coverage >= 5 cannot handle Cython `public` or `readonly` members in `.pxd` file

This is now released as part of [coverage 6.4.3](https://pypi.org/project/coverage/6.4.3).

Feature request: Detect (and warn) if in conflict with debugger

Yes, I suppose coverage could warn that a trace function is in place when it starts.

coverage reports 0% of coverage for covered files

Try using `coverage debug data` to see the paths of the files that were measured. Perhaps they are being found through another path?

coverage reports 0% of coverage for covered files

I'm not sure what the warning would be for. Coverage uses the same interpreter hooks that debuggers do. There might already be a warning. If you run pytest with the...

coverage reports 0% of coverage for covered files

Can you give me a reproducible scenario?

coverage reports 0% of coverage for covered files

@vyosypenko as always, it's *really* helpful if you can give me a reproducible scenario.

coverage reports 0% of coverage for covered files

@hdost Thanks for your reproduction, and sorry it's taken me so long to get to it. To debug these cases, it's useful to add `--debug=trace` to the coverage options, and...