Experiment with uv

Open
#90 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, python

Research direction

Start with the Makefile and .github/workflows/make-based-ci.yml, especially the referenced poetry, pyenv, diff-poetry-lockfile, and poetry-venv-implode uses. Compare the current workflow with uv and record the requested setup, installation, update, tooling, helper-task, and lockfile findings; done means the experiment and its results are documented, not necessarily a migration.

Written by the indexing model from the issue text.

Description

uv is fast rising in popularity. It's written by Astral, the same folks behind ruff.

It does everything that Poetry does when combined with pyenv for Python installation, although its Python or even pyenv's may not be suitable for production use.

This experimentation should try swapping out poetry + pyenv in the Makefile to see what changes would be necessary.

I would not consider a wholesale switch until uv is 1.0.0, at which time I'd consider it with the values of

Dominant language
Makefile
Stars
31
Forks
6
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from target/make-python-devex

All issues in target/make-python-devex

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.