Move to `pyproject.toml`

[kattni]

What is the problem or limitation you are having?

This repo is still using requirements.txt.

Describe the solution you'd like

Move to pyproject.toml, including more granular requirements for testing.

Describe alternatives you've considered

None.

Additional context

No response

[passionworkeer]

A clean migration path here would be to move runtime metadata into [project], keep test/dev requirements in optional dependency groups, and make the existing tooling read from one place only. If this template is consumed by generators, I’d also add a regression test that renders a fresh project and checks both install and test commands still work from pyproject.toml alone. That catches subtle breakage like duplicated dependency declarations or stale README/bootstrap instructions.

[freakboy3742]

@passionworkeer I'm not sure what you're trying to say/add here. The migration path is clear, and what the ticket describes - replace the usage of requirements.txt with the relevant configurations in a pyproject.toml file. What are you trying to say here?

[passionworkeer]

A low-risk migration path is to move runtime deps into [project] and test/dev docs into named optional-dependency groups first, then keep generating
equirements*.txt from pyproject.toml during transition if downstream tooling still expects them. The part I’d watch closely is template consumers: add one smoke test that creates a project from the template and installs both base and test extras, so the migration validates the rendered template, not just this repo’s own env.