mutmut VS cookiecutter-hypermodern-python

I wrote one (https://github.com/boxed/scientist) as I found the existing ones very complicated and that just gives me a bad feeling. Since I'm the author of mutmut (https://github.com/boxed/mutmut), I also made sure my implementation was 100% mutation tested before I used it in production.

I used my implementation to replace number parsing in my work project: https://kodare.net/2021/04/04/safe_number_parsing.html

Mutmut introduces a clever approach to scrutinizing your tests. It evaluates the effectiveness of your test suite by slightly altering the code after the tests have been written. If a test fails after a minor change, that's a good sign; it means the test is robust enough to catch those changes. But if the test passes even after the code change, it indicates that the test isn't effectively detecting that alteration – this is what Mutmut terms a "surviving mutant."

mutmut for mutation testing.

Hypermodern Python Cookiecutter

There is also a 'hypermodern' cookie cutter template for python projects - I've used it several times now and it works mostly out of the box:

https://github.com/cjolowicz/cookiecutter-hypermodern-python

See https://github.com/cjolowicz/cookiecutter-hypermodern-python for a template and https://cjolowicz.github.io/posts/hypermodern-python-01-setup/ for some background explanation.

I often see templates like COOKIETEMPLE or HYPERMODERN python add a separate directory called docs which either uses sphinx or mkdocs or readthedocs and has github actions for publishing docs.

Vouching for https://github.com/cjolowicz/cookiecutter-hypermodern-python .

Seems pretty similar to https://cookiecutter-hypermodern-python.readthedocs.io/

Check out Hypermodern python https://cjolowicz.github.io/posts/hypermodern-python-01-setup/ and the cookiecutter for it https://github.com/cjolowicz/cookiecutter-hypermodern-python