Skip to content

Migrate to PEP 517 build process #135

Description

@kytta

I noticed that setuptools is listed as a direct runtime dependency, but it appears to me that it is only needed for building. So, a (quite heavy) package gets pulled for no reason.

Instead of removing the dependency (and thus making it implicit), I would suggest migrating the project to PEP 517-compliant build process. IIUC it's mostly there anyway; you already have all your metadata in pyproject.toml. Final migration would mean adding a proper [build-system] section with setuptools declared in it as a build dependency, and removing setup.py. Instead of the latter, you should use PEP 517 build frontends, like python -m build or uv build, or anything else.

WDYT? I'd be happy to submit a PR if this suits you :)

Activity

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions