I am trying to understand if this is the feature I need. My problem:

I have my dependencies and dev dependencies in pyproject.toml
I have a constraint file constraints.txt
I build pip compile pyproject.toml -c constraints.txt -o requirements.txt
I build pip compile pyproject.toml --extra dev -c contraints.txt -c requirements.txt -o requirements-dev.txt

This is the most sane way I could find so both requirements.txt and requirements-dev.txt contain the same libs except for the dev ones and they respect the constraints file which are sub dependencies I need to limit but do not depend myself.

I want to move to uv lock with a uv export fallback for generating the same files as before.

From the docs:

uv supports constraints files (--constraint constraints.txt), like pip, which narrow the set of acceptable versions for the given packages.

It seems uv lock does not have the constraint mechanism described above.

I would like to perform 2 things:

Create a first uv.lock constrained by current requirements-dev.txt which will force all current versions on it

Have a workflow to run

uv lock --constraint constrains.txt  # Preferably this being configured in pyproject.toml so it is guaranteed to be true
uv export > requirements.txt
uv export --extra dev > requirements-dev.txt

Eventually I will remove the exports, but for validating the process, I will need to make sure the output versions are identical to the original versions

Is this the correct issue?

Add build-constraints support to uv lock etc. via pyproject.toml #6913

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions

Add `build-constraints` support to `uv lock` etc. via `pyproject.toml` #6913