Transition build system from `hatch` to `uv`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 42
- Forks
- 18
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
We currently rely on `hatch` for building and packaging, but `uv` is both faster and easier to use, simplifying dependency resolution and upgrade. Since we’re already using `uv` in our build and test workflow ([`build.yml`](https://github.com/projectmesa/mesa-frames/blob/main/.github/workflows/build.yml)), we should change our [`pyproject.toml`](https://github.com/projectmesa/mesa-frames/blob/main/pyproject.toml) and [`publish.yml`](https://github.com/projectmesa/mesa-frames/blob/main/.github/workflows/publish.yml) to use `uv` instead of `hatch`.
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 comparing the existing configuration in pyproject.toml and .github/workflows/publish.yml with the uv usage already present in .github/workflows/build.yml. Trace how the build and publish workflow currently invokes hatch, then update the configuration and publishing workflow to use uv. Done means packaging and publishing use uv consistently with the existing build and test workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100