Move to UV

[a-musing-moose]

🎯Aim

Convert template to use UV instead of Poetry

📕Context

Uv is a relative newcomer to the Python ecosystem but it has rapidly displaced the current tooling for a couple of reasons:

• It is extremely fast
• It can not only manage Python dependencies, but Python itself

This is on top of being able to manage project life cycles efficiently.

📝Relevant resources/doc's/people

• Migrate-to-uv is a tool that does a reasonably good job of updating the pyproject.toml of existing projects in order to make them work with uv
• Guide to migrating to UV from Astral, the authors of uv.

✅Acceptance Criteria

• Project can be installed with uv
• Documentation reflects the need for uv instead of pyenv and poetry
• Dockerfile updated to use uv to build wheel and export frozen requirements
• Github actions are updated both within the project and in the template to use uv instead of poetry.
• An ADR exists to record the transition and the reasoning.

[a-musing-moose]

@nzlaura I am sorely tempted to skip Poetry 2.0 and jump all the way to using UV instead. Thoughts?

[nzlaura]

@a-musing-moose if that's what we think we're going to be shifting to, then yep I think so 😄

I have a branch for this- but it's not entirely complete 😄

[a-musing-moose]

I think the Python onboarding story for uv. It is just a single binary install of uv itself. It will then take care of installing and using the correct version of Python for the codebase for us. No need for pyenv any more - a bonus for any devs that want to work on Windows.

So I would like to move to uv - but I guess we probably need to start a dialogue with the rest of code care and in particular @G-Rath before we go too far?