--index-url from requirements.txt is ignored

[framillien]

--index-url is ignored in requirements.txt, no issue with --extra-index-url parameter.

Look like it's related to the way IndexUrl argument is used. This argument is always initialized with a value (here) and combine always keep the previous value if present (here).

If I invert the expression in combine, my --index-url in requirements.txt is correctly used; but this is maybe not the expected way to fix it because command line parameter (if really defined) should take precedence ?

This affect both pip install and pip compile commands.

Fail with this requirements.txt:

--index-url https://my-pip-index.org/artifactory/api/pypi/pypi-custom-release/simple/

my-custom-package

Work with:

--extra-index-url https://my-pip-index.org/artifactory/api/pypi/pypi-custom-release/simple/

my-custom-package

With both commands:

uv -v --no-cache pip install requirements.txt
uv -v --no-cache pip compile requirements.in

To set the --index-url, the current workaround is to always set in on command line like:

uv -v --no-cache pip install --index-url https://my-pip-index.org/artifactory/api/pypi/pypi-custom-release/simple/ requirements.txt

[charliermarsh]

Will take a look, thanks!

[framillien]

(description edited because it's more related to arguments default values rather than IndexLocations default values)

[PetterS]

Is it possible to add a private PyPI in the pyproject.toml in a standardized way that uv understands? That is quite important in many corporate settings. poetry supports this via the non-standard [[tool.poetry.source]] so that works well for corporations.

[zanieb]

Not yet, but we will support persistent configuration of registries in the future.

[framillien]

Thanks for the quick fix

[PetterS]

Not yet, but we will support persistent configuration of registries in the future.

@zanieb is there a tracking issue for that feature I can subscribe to?