While gradually improving the setup of a couple local Python projects with your checker, pre-commit hooks, pytest, etc, I notice the presence of a file .gitignore actually is not yet a criterion considered.
However I think this would be a nice addition, as such a file prevents the accidental admission of unwanted files to the commit history. Examples include temporary / swap files left by (code) editors in general; .pyc files, cache data of pytest and mypy more specific to projects of and around Python. The presence of already compiled .gitignore files (example GitHub), or generators to consider one or multiple causes / sources (e.g., vim and python) of the files irrelevant to commit history eases to adjust such a file to personal preferences / group policy.
To me preferentially to section General / PY because it is of even more general nature than than PyProject / PP alone.
While gradually improving the setup of a couple local Python projects with your checker, pre-commit hooks, pytest, etc, I notice the presence of a file
.gitignoreactually is not yet a criterion considered.However I think this would be a nice addition, as such a file prevents the accidental admission of unwanted files to the commit history. Examples include temporary / swap files left by (code) editors in general; .pyc files, cache data of pytest and mypy more specific to projects of and around Python. The presence of already compiled
.gitignorefiles (example GitHub), or generators to consider one or multiple causes / sources (e.g.,vimandpython) of the files irrelevant to commit history eases to adjust such a file to personal preferences / group policy.To me preferentially to section General /
PYbecause it is of even more general nature than than PyProject /PPalone.