python3.7-arm64 is not available about setup-python

[cclauss]

GitHub Actions blog:

Over the next 12 weeks, jobs using the macos-latest runner label will migrate from macOS 12 (Monterey) to macOS 14 (Sonoma).

https://github.blog/changelog/2024-04-01-macos-14-sonoma-is-generally-available-and-the-latest-macos-runner-image

See workaround: actions/runner-images#9770 (comment)

[woodruffw]

This is causing downstream breakage in some core Python dependencies: psf/cachecontrol#333

3.7 is technically EOL, but many core Python tools (like pip itself) have an compatibility policy that includes 3.7. As such, this should probably be supported on arm64 macOS runners until 3.7 is widely dropped (or at least from pip and its dependencies, like cachecontrol).

[jvesely]

(Or potentially: could the ARM macOS runner use the x86 build? ARM macs have mature emulation support via Rosetta, so running the x86 3.7 build should work.)

You can set architecture: x64 to use x64 python on aarch64 runners. I'd be nice if that was the default for setup-python but you'll probably hit #855

[shawnbrown]

I'm also seeing this (with python-version: 3.7):

Run actions/setup-python@v5
  with:
    python-version: 3.7
    cache: pip
    check-latest: false
    token: ***
    update-environment: true
    allow-prereleases: false
Installed versions
  Version 3.7 was not found in the local cache
  Error: The version '3.7' with architecture 'arm64' was not found for macOS 14.4.1.
  The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

[aparnajyothi-y]

Hello @jvesely, Thank you for creating this issue and we will get back to you once we have some feedback on this :)

[mayeut]

If I'm not mistaken, Python 3.7 has never been supported on macOS arm64 and upstream support in CPython has only been added for 3.8+ (in 3.8.10 for the 3.8 branch).
It might be simpler to stick to macos-11/12/13 label if you want to test python<3.8

xref actions/runner-images#9770

[mikedh]

For me this looks like it's probably that the macos-latest Github action runner appears to have switched to an M1 ARM mac, where at least last week macos-latest was an x86 mac.

[woodruffw]

For me this looks like it's probably that the macos-latest Github action runner appears to have switched to an M1 ARM mac, where at least last week macos-latest was an x86 mac.

This is the source of my observed breakage as well. It's perfectly fine for there to never be an arm64 build of Python 3.7, but it would be nice to have a clearer message to the effect of "this is happening because the runner is now an ARM runner, not because 3.7 has disappeared from x86 runners" 🙂

(Or potentially: could the ARM macOS runner use the x86 build? ARM macs have mature emulation support via Rosetta, so running the x86 3.7 build should work.)

[cclauss]

Does the CPython Core Team support Python 3.6 or 3.7 running on macOS ARM? I thought that they did not.

• https://docs.python.org/3.9/whatsnew/3.9.html#macos-11-0-big-sur-and-apple-silicon-mac-support
• python/cpython#85272
• python/cpython#25806
• python/cpython#85272 (comment) No on Py37
• python/cpython#85272 (comment) Again no on Py37

This is why I created the workaround:

• actions/runner-images#9770 (comment)

@mikhailkoliada