Hatch test does not find private package dependency, while it is found in the default environment

[bkerkhof]

I have a project that has a dependency on a package stored in a private repository, which is not found when running hatch test.

The relevant pyproject.toml file sections are:

[project]
dependencies = [
  "my-dependency",
  "numpy",
  "matplotlib"
]

[tool.hatch.envs.hatch-test]
# Show extra information onscreen
extra-args = ["-vv"]
extra-dependencies = [
  "my-dependency",
  "teamcity-messages"
]

The parameters for PIP are set in the hatch.toml configuration file:

[envs.default.env-vars]
PIP_INDEX_URL="https://private-server/pypi/simple"
PIP_TRUSTED_HOST="private-server"

[envs.hatch-test.env-vars]
PIP_INDEX_URL="https://private-server/pypi/simple"
PIP_TRUSTED_HOST="private-server"

Hatch seems to indicate that the environment variables are properly set:
hatch env show

hatch test -s

When running hatch shell, the virtual environment is created and all dependencies are resolved, including my-dependency. This can be verified using pip list, as well as by actually using the package.

When running hatch test, it complains that the dependency cannot be resolved.

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

Am I missing anything here? This is using hatch 1.12.0 and hatchling 1.25.0.

[bkerkhof]

And the answer is that hatch test doesn't use pip but uv by default.

Setting installer="pip" for the hatch-test environment seems to do the trick. Unfortunately, uv doesn't support something like PIP_TRUSTED_HOST for a self-signed SSL certificate, so it ends up being slower -- but functional.

[ofek]

Thanks! This will continue to be the default for internal environments until some planned improvements to pip are implemented.