Switch from `pipx` and `venv` to `uv` and friends
Open
Nobody has claimed this yet.
43 lvl: complex
- Dominant language
- Makefile
- Stars
- 106
- Forks
- 190
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
Links of affected pages in Plone Documentation, if any.
No response
Description
Consider switching from pipx to uv and its tools for installing packages and creating a virtual environment.
@davisagli feel free to edit this description or add comments.
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
No affected documentation pages, files, or tests are identified. Search the documentation for references to pipx and venv, then determine which installation and virtual-environment instructions are in scope; done means the relevant guidance consistently reflects the agreed uv approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100