Micha Reiser

I plan to work on this on Monday except someone beats me to it. Appreciate any pointers.

> > Hm this looks to be working in GitHub actions with `setup-python` over here [astral-sh/uv/actions/runs/7944040120/job/21689087415?pr=1611](https://github.com/astral-sh/uv/actions/runs/7944040120/job/21689087415?pr=1611) > > When called from within tox [tox-dev/tox-uv#19](https://github.com/tox-dev/tox-uv/pull/19) seems it fails though.... This seems...

According to pep514, `py` already makes use of the registry information. Therefore, implementing PEP514 is unlikely to help when trying to discover all python versions. > When installed on Windows,...

> We _do_ correctly find `python.exe` with #1381. I think #1381 only fixes the problem for `find_default_python` but not when calling `uv --python 3.8` where 3.8 is the default python...

I think this is the same issue as https://github.com/astral-sh/uv/issues/1392 except that it tries to pick the statically linked musl instead of the dynamic. We're working with axo on a fix....

We use cargo-dist to generate the installer and the latest version had a bug where it failed to generate the necessary mappings for aarch64-musl.

That sounds like it can't find python for some reason. I can take a look

I wonder if it's related to the venv "trick". The trampoline (it creates the call that failes above) should construct the following command: ```bash \python.exe \black.exe ``` where `path_to_scripts` is...

We can figure it out together. I know very little about how venv works on windows ;) > is that the python.exe executable isn't located in the same place on...

I'm just guessing but I get the impression that the tests run into the same problem because they run without activating a venv?