python-trio / python-trio/trio

Switch to `pylock.toml` from our `test-requirements.txt` lockfile

Open
#3,437 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
7.3k
Forks
431
Avg merge
2d 17h
Merged PRs (30d)
6

Description

Actually, there's a standardized lockfile now. Pip's support for it is in beta, but I figure we can switch to it whenever. In particular, it looks like we can swap pip compile requirements.in --universal -o requirements.txt to uv pip compile requirements.in -o pylock.toml (I don't know if we can do test-requirements.in and docs-requirements.in in the same file...)

Originally posted by @A5rocks in https://github.com/python-trio/trio/issues/3188#issuecomment-4413943729

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the current requirements.in, test-requirements.in, and docs-requirements.in inputs and the pip-compile command that produces requirements.txt. Check uv pip compile's pylock.toml support and how multiple input files should be represented; done means the existing lockfile process is replaced with a working pylock.toml-based process.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system, tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.