uv-import-constraint-dependencies 0.1.2

Import constraints.txt into pyproject.toml as tool.uv.constraint-dependencies

uv-import-constraint-dependencies

A CLI tool to import constraints.txt files into pyproject.toml as tool.uv.constraint-dependencies.

Overview

This tool reads a pip constraints file (local or remote) and adds the pinned dependencies to your pyproject.toml in the format expected by the uv package manager.

Installation

uv tool install uv-import-constraint-dependencies

Or with pip:

pip install uv-import-constraint-dependencies

Usage

Basic Usage

Import constraints from a local file:

uv-import-constraint-dependencies -c constraints.txt

Import constraints from a remote URL:

uv-import-constraint-dependencies -c https://example.com/constraints.txt

Options

Option	Short	Description
--constraints	-c	Path or URI to constraints.txt file (required)
--pyproject	-p	Path to pyproject.toml file (default: pyproject.toml)
--custom-constraints	--cc	Path to local custom constraints file for overriding base constraints
--merge		Merge with existing constraint-dependencies instead of replacing
--version		Show version information
--help		Show help message

Examples

Custom pyproject.toml path:

uv-import-constraint-dependencies -c constraints.txt -p path/to/pyproject.toml

Merge with existing constraints instead of replacing:

uv-import-constraint-dependencies -c constraints.txt --merge

Override base constraints with local customizations:

uv-import-constraint-dependencies -c https://example.com/constraints.txt --cc custom-constraints.txt

Behavior

Replace Mode (Default)

By default, all existing constraint-dependencies in pyproject.toml are replaced with the new ones from the constraints file.

Merge Mode (--merge)

When using --merge, new constraints are merged with existing ones in tool.uv.constraint-dependencies:

• New packages are added
• Existing packages are updated with the new version specifier
• Packages not in the new constraints file are preserved
• Constraints are sorted alphabetically

Custom Constraints (--cc)

The --cc (or --custom-constraints) option allows you to override specific packages from the base constraints file with local customizations. This is useful when:

• You use a shared/remote constraints file but need different versions for specific packages
• You want to test newer versions of certain dependencies without modifying the base file

How it works:

1. Base constraints are loaded from -c (can be local or remote)
2. Custom constraints from --cc are merged on top (custom takes precedence)
3. The combined result is then merged with or replaces existing pyproject.toml constraints (depending on --no-merge)

Example workflow:

# Remote base constraints + local overrides
uv-import-constraint-dependencies -c https://example.com/constraints.txt --cc custom-constraints.txt

Example custom-constraints.txt:

# Override requests version from base constraints
requests==2.32.0

# Add a package not in base constraints
my-internal-package==1.0.0

Constraints File Format

The tool supports standard pip constraints file format:

# Comments are ignored
requests==2.31.0
flask>=2.0.0,<3.0.0
numpy==1.24.3 ; python_version >= "3.9"  # Inline comments are stripped
urllib3>=1.26.0

# Include directives are skipped
-r requirements.txt
-c other-constraints.txt

Output Format

The constraints are written to pyproject.toml as:

[tool.uv]
constraint-dependencies = [
    "flask>=2.0.0,<3.0.0",
    "numpy==1.24.3 ; python_version >= \"3.9\"",
    "requests==2.31.0",
    "urllib3>=1.26.0",
]

Requirements

• Python >= 3.10

Dependencies

• click >= 8.0 - CLI framework
• tomlkit >= 0.12 - TOML manipulation with formatting preservation

License

MIT