Skip to content

Maintaining the example build backend specifiers #1886

@ncoghlan

Description

@ncoghlan

Issue Description

In #1880, questions were raised regarding the maintainability of the example build backend dependencies. Specifically:

  • how to handle backends that recommend upper bounds on the backend version (while tools that create per-package build environments can handle those without issue, they are a potential problem for build systems that aim to create unified build environments, such as those for Linux distros and from-source stack building projects like fromager)
  • how to ensure we're not recommending excessively outdated versions of the backends

Some flavour of automation could help with the latter problem, but the former problem is a trickier one.

Code of Conduct

  • I am aware that participants in this repository must follow the PSF Code of Conduct.

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