Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reporting should be possible with just the public API #921

Open
nedbat opened this issue Jan 15, 2020 · 2 comments
Open

Reporting should be possible with just the public API #921

nedbat opened this issue Jan 15, 2020 · 2 comments
Labels
api Changes to the public API enhancement New feature or request

Comments

@nedbat
Copy link
Owner

nedbat commented Jan 15, 2020

Is your feature request related to a problem? Please describe.
People (like coveralls) end up using internal details of coverage.py because they can't get everything they need from the public supported API. Then when the internals of coverage.py change, their code breaks.

Describe the solution you'd like
We should extend the public API to support their needs. One good litmus test would be: if coverage.py's own reporting commands (html, xml, json, report) could be written with only the public API.

@nedbat nedbat added enhancement New feature or request api Changes to the public API labels Jan 15, 2020
@TheKevJames
Copy link

Alright, well, to get this conversation started, this stemmed from my work updating coveralls to support v5 of coverage.py. PR link. More generally, our usage of the coverage.py library is pretty much confined to this file -- note that there's a whole lot of fallback logic there for supporting v4 and v3 of coverage, which we've not yet deprecated support for.

@nedbat
Copy link
Owner Author

nedbat commented Nov 15, 2021

See #1273

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Changes to the public API enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants