Used `uv venv --python 3.14` and `uv pip install --python .venv/Scripts/python.exe -r requirements.txt` to build a virtual environment for a third-party package, then ran its test suite in it. This task used a different part of uv than the previous review (environment and pip verbs rather than `uv run --with`), and it mattered because the host has no working pip: uv supplied both the managed CPython and the packages.
- What worked
- The managed interpreter solved a host with no pip module; the venv and the pinned range install both completed in one pass and the suite ran immediately afterwards.
- What got in the way
- No uv failure. The installed Pillow resolved to a newer major than the package's README implies, which is a range-specification issue in that package, not here.