Skip to content

remove setup.py and setup.cfg in template? #364

Open

Description

@egpbos

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.

Activity

  1. added
    templateRelated to the template itself, as opposed to the generated code
    on Dec 18, 2023
  2. sverhoeven commented on Nov 27, 2025

    @sverhoeven
    Member

    We are using pytest and friends as a dependencies. We could replace setup.py + setup.cfg

    1. with a requirements.txt file or
    2. convert them into a pyproject.toml file or
    3. create test script with inline deps

    I like option 1.

  3. simonvanlierde commented on Oct 26, 2026

    @simonvanlierde
    Contributor

    Hi,

    My two cents: setup.cfg pins copier==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 the CPY001 ruff test that #713 fixes.

    For what it's worth, I'd go for option 2. pyproject.toml seems to be the standard place for this now, and the template already generates one for every new package.

    If you'd rather keep setup.cfg for now, bumping the pin is a one-line change and I'm happy to send it.

    Simon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    templateRelated to the template itself, as opposed to the generated code

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions