ImperialCollegeLondon / ImperialCollegeLondon/python-template
Make build backend configurable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Following on from discussion #526 - we should provide a cookiecutter option that will select which build backend is used.
Options we should include:
- setuptools + setuptools-scm (current option)
- uv-build
- Flit
- Hatchling
Worth noting that the details of how this is implemented will change if we update this whole tool to use uv init under the hood (see #572)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading discussion #526 and the related issue #572 to understand the existing build setup and whether uv init will replace it. Then locate the cookiecutter configuration and build-generation entry points. Done means selecting setuptools plus setuptools-scm, uv-build, Flit, or Hatchling produces a valid project without conflicting with the planned uv init approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100