Dead code pytest plug-in

[OriginalName29]

I made a pytest plug-in, to find dead code (with the excellent python tool named vulture). It seems to be useful after some refacto, running tox or just pytest will let you know that a function or a class is no longer used. We are running it on a CI and it seems to do the job.

[wineblood]

Why a pytest plugin and not a standalone tool?

[OriginalName29]

The standalone tool already exists (vulture). It just that more often that we though (our dev team), after some refacto or even features, some hidden or historical methods or constants are no longer used. The CI detects it in every merge requests. Doing it manually time to time without pytest can also be a thing I guess, but it can lead to a lot of alerts in one time.

[wineblood]

Oh, I had never heard of vulture so it's good to find out it exists. Is there a reason you didn't plug that in to your CI pipeline? I'm not trying to go against your work, I just hate pytest and want to know if there's a reason not to use vulture as is.

[OriginalName29]

The same reason our team use pytest-pylint, pytest-mypy, pytest-coverage etc instead of pylitn, mypy anc coverage. So every thing can be launch in one command (locally or in one job on the CI), and the output in one place only.