UCL-ARC / UCL-ARC/python-tooling
Given that we are using `uv`, should the template include a `uv.lock`?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 62
- Forks
- 10
- Avg merge
- 7d 6h
- Merged PRs (30d)
- 6
Description
What is the Topic of Your Question
Other
Add Your Question Below
The general advice when working with uv is to include a uv.lock. We currently provide a pyproject.toml with some optional-dependencies but without a lock file. We could even use this prek hook to remind users to keep it up-to-date https://github.com/astral-sh/uv-pre-commit.
Contributor guide
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 reviewing the template's pyproject.toml, especially its optional-dependencies, and compare the project’s current uv workflow with the linked uv-pre-commit hook. Determine whether the template should include a uv.lock and whether the hook belongs in the template; done means the decision and resulting template changes are documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100