aws.amazon.com/cli's registry artifacts (all platforms) are pkgx mirrors built against python 3.11.15: the venv holds lib/python3.11/site-packages and cpython-311 extension modules, and bin/aws names python@3.11. The registry only has python.org 3.13.x and 3.14.x, because the pkgx mirror keeps the 20 most recent patch releases and those are all 3.13/3.14. Its catalog constraint (python.org>=3.11<3.15) resolves to 3.14, which cannot load awscli.
python.org 3.11 is not in the registry, so pkgx-mirrored Python CLIs (aws-cli) cannot run
#237python.org 3.11.16 and 3.12.14 are now in the registry (darwin-arm64, linux-x86-64, linux-arm64; mirrored from pkgx in run 37177834484). ec4697a makes the pkgx mirror keep the newest patch of older minor lines so they stay available, and 24509be makes the installer read the interpreter version from the pkgx shebang and install it. Verified in a clean scratch project: pantry install aws.amazon.com/cli then aws --version → aws-cli/2.34.15 Python/3.11.16 Darwin/27.0.0 source/arm64.
Sign in to comment on this issue.