in conda-lock, the yml file has supports for custom pypi indices using pip-repositories:

from conda-lock readme:

channels:
  - conda-forge
pip-repositories:
  - http://$PIP_USER:[email protected]/api/pypi/simple
dependencies:
  - python=3.11
  - requests=2.26
  - pip:
    - fake-private-package==1.0.0

In unidep I can support it using

[[tool.uv.index]]
url = "http://$PIP_USER:[email protected]/api/pypi/simple"

That works for unidep install.

But now I try to unidep conda-lock to generate a lock file. The temporary environment.yml file generated does not include the pip-repository, and so the next step of creating the lock file is failing, because it can't file the fake-private-package.

Best solution, I think

Native support pip-repositories in [tool.unidep], and pass it to uv when installing packages as extra index.

What I can live with

Have a pip-repositories in [tool.unidep] but only for copying it into the temporary environement.yml file. This would not have any effect on unidep install, only on unidep conda-lock. I would still have to manage the [[tool.uv.index]] for using unidep install myself.