TST/DEP: drop pytest-cov in favor of using coverage.py directly - #18879

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

• Do the proposed changes actually accomplish desired goals?
• Do the proposed changes follow the Astropy coding guidelines?
• Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
• Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
• Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
• Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
• Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
• Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
• At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

👋 Thank you for your draft pull request! Do you know that you can use [ci skip] or [skip ci] in your commit messages to skip running continuous integration tests until you are ready?

Now computing coverage is 2 steps, versus 1 with pytest-cov ?

yes. This seems like a very reasonable price to pay to rid ourselves of a dependency, in my opinion. However, I did discover a blocking issue with this approach, reported upstream at OpenAstronomy/github-actions-workflows#330

I'm 🤷 on this. I've never had an issue with pytest-cov but I appreciate wanting to streamline dependencies.

FWIW I can't say I never had any issue with using coverage directly, but I have yet to encounter a problem that pytest-cov actually solves for me. Meanwhile, it has created problems of its own.

Hi humans 👋 - this pull request hasn't had any new commits for approximately 4 months. I plan to close this in 30 days if the pull request doesn't have any new commits by then.

In lieu of a stalled pull request, please consider closing this and open an issue instead if a reminder is needed to revisit in the future. Maintainers may also choose to add keep-open label to keep this PR open but it is discouraged unless absolutely necessary.

If this PR still needs to be reviewed, as an author, you can rebase it to reset the clock.

If you believe I commented on this pull request incorrectly, please report this here.

has created problems of its own.

I'm interested. What problems?

Sorry this got drowned in other notifications... I don't recall any specific incident regarding pytest-cov within astropy's CI, though I do remember seeing but general observations

• any dependency introduces risks (supply chain attack) and/or maintenance burden
• the fact that pytest-cov has major releases with breaking changes is evidence that the shim it provides over coverage.py isn't always free for ever. Of course the changelog is also evidence that this software isn't bug free (what is ?).

If getting rid of it has no impact, then 🤷 sure :)

@zacharyburnett or @Cadair , any opinions here? Thanks, all!

Hi humans 👋 - this pull request hasn't had any new commits for approximately 6 months. I plan to close this in a month if the pull request doesn't have any new commits by then.

In lieu of a stalled pull request, please consider closing this and open an issue instead if a reminder is needed to revisit in the future. Maintainers may also choose to add keep-open label to keep this PR open but it is discouraged unless absolutely necessary.

If this PR still needs to be reviewed, as an author, you can rebase it to reset the clock.

If you believe I commented on this pull request incorrectly, please report this here.