I have an idea of what this might look like, but do you have any examples I can crib from?

spoiler alert: Python isn’t written in Python

Literally it's best feature, because then you can download a binary and guarantee that with that binary, you have a working python virtualenv on every platform UV supports.

This page said it's written in Rust. Is this the same UV?

That means it can't be maintained by the community it's serving. For those skilled in both Rust and Python can understand why it would appear as the best thing since sliced bread.

What about for those not skilled in Rust? Should we also learn 15 other coding languages while we are at it?

wreck is written in Python and manages dependencies. via hierarchy of requirements files, not TOML. It's venv aware. For Python package authors.

it does, I use it every day

this is the standard https://packaging.python.org/en/latest/specifications/dependency-groups/

UV has a shitload of features. I've only ever really used it for making virtualemvs for easier cross platform compatibility, but even just for that, there's tons of options related to which packages, from where, etc.

tl:dr probably, although differentiating between "deploy" and "dev" installs is the task of the package config which UV doesn't (to my knowledge) replace in any way.

wreck can. It's venv aware. Takes full advantage of hierarchical requirement files. Is intuitive. The learning curve is minimal. Written in Python.

[[tool.wreck.venvs]]
venv_base_path = '.venv'
reqs = [
    'requirements/pip',
    'requirements/pip-tools',
    'requirements/prod',
    'requirements/dev',
    'requirements/manage',
    'requirements/kit',
    'requirements/mypy',
    'requirements/tox',
]
[[tool.wreck.venvs]]
venv_base_path = '.doc/.venv'
reqs = [
    'docs/requirements',
    'docs/pip-tools',
]

[tool.setuptools.dynamic]
dependencies = { file = ['requirements/prod.unlock'] }
optional-dependencies.pip = { file = ['requirements/pip.lock'] }
optional-dependencies.pip_tools = { file = ['requirements/pip-tools.lock'] }
optional-dependencies.dev = { file = ['requirements/dev.lock'] }
optional-dependencies.manage = { file = ['requirements/manage.lock'] }
optional-dependencies.docs = { file = ['docs/requirements.lock'] }

reqs fix --venv-relpath='.venv'

reqs fix --venv-relpath='.doc/.venv'

From *.in requirements files would produce *.unlock and *.lock files for venv .venv. Package versions are sync'ed within all requirements files within that venv.

I know it's not the point of this comment, but I'll check harlequin out