pytest-coverage exists but is pytest-cover, not pytest-cov

[ianw]

Hi,

I recently found a typo issue in requirements, with pytest-coverage being used instead of pytest-cov.

AFAICT https://pypi.org/project/pytest-coverage/ is blank package with a dependency on https://pypi.org/project/pytest-cover/, which is an abandoned fork of pytest-cov after changes were merged back into the main project.

I understand there's always a bit of tension between historical archives and current operation, but given pytest-cov and pytest-coverage are very close, and that pytest-cover is installing something that is sort-of pytest-cov but not current, I do feel like this is probably causing unnecessary confusion.

AFAICT these are all under the same ownership? Given they are all within typo-distance of each other, I'd like to make the suggestion that these are perhaps past their useful life, in that they cause more problems now than any archival history is worth.

Anyway, thank you for your work which I have used in many projects.

[ionelmc]

Well yeah, I could delete them, or just publish new "empty" releases that depend on pytest-cov. I think the later is more transparent about what is going on. pytest-coverage is an alias to pytest-cover anyway.

[ianw]

Right, it would be helpful if the pypi page had some help as I had to dig into the installed metadata file to figure out what was going on 😀

Personally I think remove them as they feel like juicy typo-squat targets and maybe them just not being a thing is best long term. But up to you, I thought it worth pointing out it can be a bit confusing for users. Thanks

[RonnyPfannschmidt]

it seeems sensible to replace the packages with stand ins that depend on pytest-cov and trigger warnings, so people notice and an fix their deps

[ionelmc]

I like the idea of warnings, not sure how to implement. Any suggestions?

[The-Compiler]

First thing coming to mind is to make pytest-cover{,age} depend on pytest-cov, but also register their own trivial pytest plugin which essentially does (untested):

def pytest_configure():
    warnings.warn("pytest-cover{,age} is replaced by pytest-cov, please uninstall it and depend on pytest-cov instead.", DeprecationWarning)

or somesuch.

[ianw]

Also would be nice to archive (https://blog.pypi.org/posts/2025-01-30-archival/) pytest-cover and pytest-coverage after any last changes like warnings. Will indicate to users who hit pypi what's going on, but also will help things like static dependency scanners that will see you using an archived package, which might also help.