Skip to content

discrepancy between coverage of scipy and scipy-stubs #94

Description

@jorenham

On https://python-type-checking.com/prioritized/index.html, scipy-stubs has ~100% coverage, but scipy itself has only ~50% (parameter) coverage in the "w/ Typeshed" column. The strange thing is that scipy-stubs enforces in CI that it indeed covers 100% of the scipy modules, both public and private. So I would have expected that ~50% to be ~100%. And even if you exclude everything under doc/, the benchmarks, and the vendored projects, then it'll only go up to ~54% (parameter) coverage.

So any idea what's going on here? Maybe the script is double-counting or something? I tried hacking away at it myself, but wasn't able to figure it out.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions