Hatch installing Pythons even though they are already installed

[kpfleming]

I'm working on converting an existing system over to using Hatch-installed Python, instead of building/installing them myself.

In the first phase container, I've set HATCH_CONFIG="/hatch/config.toml, and that file contains:

[dirs]
data = "/hatch/data"
cache = "/hatch/cache"
python = "/hatch/python"

[dirs.env]
virtual = "/hatch/virtual"

During the first container phase, I run the command hatch python install 3.8 3.9 3.10 3.11 3.12, and this has the expected result. Hatch installs all five versions, with the result looking like this:

$ ls -l /hatch/python
total 5
drwxr-xr-x 3 root root 4 May 18 16:05 3.10
drwxr-xr-x 3 root root 4 May 18 16:05 3.11
drwxr-xr-x 3 root root 4 May 18 16:05 3.12
drwxr-xr-x 3 root root 4 May 18 16:05 3.8
drwxr-xr-x 3 root root 4 May 18 16:05 3.9

In the second phase, when a Python package source directory has been mounted into the container (containing a pyproject.toml with various environments configured), I run hatch env create lint. That environment is configured with python = "3.12", and in spite of that already being installed, Hatch installs it again. The PATH in that second phase container looks like this:

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/hatch/python/3.8/python/bin:/hatch/python/3.9/python/bin:/hatch/python/3.10/python/bin:/hatch/python/3.11/python/bin:/hatch/python/3.12/python/bin"

I run with -vvvvv but the Python distribution handling code doesn't appear to contain any code which would emit verbose messages, so I'm at a bit of a loss to figure out what else would be required.

[kpfleming]

This appears to be related to #1280.

[kpfleming]

I'll mark this resolved; it was a combination of local configuration issues which prevented Hatch from being able to locate the previously-installed Python interpreters.

[ofek]

Thanks for following up!