#23455 Custom pip indexes stopped working, when using uv resolver Issue created by lowvoltage Describe the bug Indexes defined in

[python-repos]
indexes.add = [
...

no longer work, when using the

uv

resolver Pants version

main

OS MacOS Additional info Seems to be caused by #23443 CC: @happy-kitchen-89482 Reproducible example

python_requirement(
    requirements=["aiocometd==0.4.5+hs1"],
)

[GLOBAL] pants_version = "2.32.0" backend_packages = [ "pants.backend.python", ] [python] interpreter_constraints = ["==3.13.*"] enable_resolves = true default_resolve = "python-default" resolver = "uv" [python.resolves] python-default = "toolchain/lockfiles/python-default.lockfile" [python-repos] indexes.add = [ "https://build-storage.master.hs.ai/build_artifacts/public_pip", ] [uv] extra_env_vars = [ # Search for every package name across all indexes, exhausting the versions from the first index # before moving on to the next "UV_INDEX_STRATEGY=unsafe-best-match", ]

❯ PANTS_SOURCE=../pants  pants generate-lockfiles --resolve=python-default
Pantsd has been turned off via Env.
19:00:55.31 [INFO] Completed: Generate uv lockfile for python-default (1.3s)
19:00:55.31 [ERROR] 1 Exception encountered:

Engine traceback:
  in `generate-lockfiles` goal

ProcessExecutionFailure: Process 'Generate uv lockfile for python-default' failed with exit code 1.
stdout:

stderr:
Using CPython 3.13.12
  × No solution found when resolving dependencies:
  ╰─▶ Because there is no version of aiocometd==0.4.5+hs1 and your project
      depends on aiocometd==0.4.5+hs1, we can conclude that your project's
      requirements are unsatisfiable.

pantsbuild/pants