Open
Labels
templateRelated to the template itself, as opposed to the generated codeRelated to the template itself, as opposed to the generated code
Description
The template has a setup.py and setup.cfg file in the root. I wasn't aware that the template even needs these; it is not a Python package, is it? Does anybody ever pip install it?
If not, I suggest we remove those files and any others that may be unnecessary for non-packages.
Metadata
Metadata
Assignees
Labels
templateRelated to the template itself, as opposed to the generated codeRelated to the template itself, as opposed to the generated code
Activity
sverhoeven commentedon Nov 27, 2025
We are using pytest and friends as a dependencies. We could replace setup.py + setup.cfg
I like option 1.
simonvanlierde commentedon Oct 26, 2026
Hi,
My two cents:
setup.cfgpinscopier==9.2.0, so the template's own tests run against a copier users no longer install. The latest is 9.19.1. I ran the full suite with it and nothing breaks; the only failure is theCPY001ruff test that #713 fixes.For what it's worth, I'd go for option 2.
pyproject.tomlseems to be the standard place for this now, and the template already generates one for every new package.If you'd rather keep
setup.cfgfor now, bumping the pin is a one-line change and I'm happy to send it.Simon