markdown-it-py
markdown-it-py copied to clipboard
Split 'testing' extra to 'testing' and 'coverage'
Describe the problem/need and solution
Hi!
I maintain some Executable Books packages in Fedora (MyST-Parser and whatever it depends on).
As a downstream consumer I'd love to build the RPM package as automatically as it gets, without tweaking the upstream configuration too much.
During the RPM build I want to run the tests as they are the best indicator of the package health but from my POV coverage is not important at all - it doesn't say anything of the package quality on my level. So with the current extras I need to remove python-cov and coverage from testing extra to get only the "core" testing packages.
It would help me to have coverage split to another extra. I guess it would be beneficial also to the other distros package maintainers.
I'll be happy to send a PR if you agree with this idea.
Guide for implementation
No response
Tasks and updates
No response
Thanks for opening your first issue here! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.
If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).
Welcome to the EBP community! :tada: