Pinning packages to an index with `uv` does not work

[valentinoli]

uv supports pinning a package to an index. I tried this with hatch and it works:

[tool.hatch.envs.default]
installer = "uv"
dependencies = ["my-package"]

[tool.uv.sources]
my-package = { index = "foo" }

[[tool.uv.index]]
name = "foo"
url = "https://pkgs.dev.azure.com/foo/bar/_packaging/baz/pypi/simple/"
explicit = true

However, with hatch-pip-compile it does not work anymore:

[tool.hatch.envs.default]
type = "pip-compile"
pip-compile-resolver = "uv"
pip-compile-installer = "uv"
dependencies = ["my-package"]

[tool.uv.sources]
my-package = { index = "foo" }

[[tool.uv.index]]
name = "foo"
url = "https://pkgs.dev.azure.com/foo/bar/_packaging/baz/pypi/simple/"
explicit = true

I get an error that looks like:

  × No solution found when resolving dependencies:
  ╰─▶ Because my-package was not found in the package registry and you require my-package, we can conclude
      that your requirements are unsatisfiable.

[juftin]

Is this a feature of uv pip compile or just uv projects?

[valentinoli]

It is a regular uv feature

https://docs.astral.sh/uv/configuration/indexes/#pinning-a-package-to-an-index

[juftin]

Ahh! Figured out the issue here @valentinoli. In order to work with pip-compile / uv pip compile, hatch-pip-compile creates a temporary requirements.in file and runs compile on that (this is because uv / pip-compile don't understand hatch environments).

This all happens here:

hatch-pip-compile/hatch_pip_compile/plugin.py

Lines 139 to 153 in f51afef

	with tempfile.TemporaryDirectory() as tmpdir:
	tmp_path = pathlib.Path(tmpdir)
	input_file = tmp_path / f"{self.name}.in"
	output_file = tmp_path / "lock.txt"
	input_file.write_text("\n".join([*self.dependencies, ""]))
	if self.piptools_lock_file.exists():
	shutil.copy(self.piptools_lock_file, output_file)
	self.piptools_lock_file.parent.mkdir(exist_ok=True, parents=True)
	cmd = self.resolver.get_pip_compile_args(
	input_file=input_file,
	output_file=output_file,
	)
	self.plugin_check_command(cmd)
	self.piptools_lock.process_lock(lockfile=output_file)
	shutil.move(output_file, self.piptools_lock_file)

I think the resolution might be to temporarily copy the pyproject.toml file alongside the temporary requirements.in when generating the Lock.

I will look into getting a fix out for this soon. Just an FYI, I just welcomed my first child into the family a couple weeks ago and so my response time will be a bit slower than usual.

[juftin]

So it looks like the issue here is with explicit indexes. Since hatch-pip-compile uses a requirements.in file instead of a pyproject.toml file to generate LockFiles, it doesn't understand explicit indexes.

Consider the following requirements.in:

uv~=0.6.3
test-123-test==1.0.0

uv comes from https://pypi.org/simple/, and test-123-test comes from https://test.pypi.org/simple/

So if you run uv pip compile requirements.in with the following pyproject.toml it will fail:

[tool.uv.sources]
test-123-test = { index = "test" }

[[tool.uv.index]]
name = "test"
url = "https://test.pypi.org/simple/"
explicit = true

❯ uv pip compile requirements.in
  × No solution found when resolving dependencies:
  ╰─▶ Because test-123-test was not found in the package registry and you require test-123-test==1.0.0, we can conclude that your requirements are unsatisfiable.

However the following changes to the pyproject.toml will allow it to work:

[[tool.uv.index]]
name = "test"
url = "https://test.pypi.org/simple/"

❯ uv pip compile requirements.in
Resolved 2 packages in 223ms
# This file was autogenerated by uv via the following command:
#    uv pip compile requirements.in
test-123-test==1
    # via -r requirements.in
uv==0.6.3
    # via -r requirements.in

Unfortunately this is a bug (or maybe intended behavior?) on the uv side and not within hatch-pip-compile

[juftin]

Opened astral-sh/uv#11848 on uv as I believe this is a feature/bugfix that belongs there

[david-rommedahl]

First of all congratulations on the arrival of your child @juftin!

I saw that this issue is still open and might be something that you are working on. I was wondering if you think that there is any possibility of including the explicit indexes functionality in hatch-pip-compile through some sort of workaround? This would be very useful, if at all possible.