Skip to content

python3.7-arm64 is not available #856

Closed
Closed
python3.7-arm64 is not available#856
Assignees
v-aparnajyothi-y
Labels
bugSomething isn't working

Description

@jvesely
jvesely
opened on Apr 26, 2024

Description:
Using default python-architecture for python 3.7

Action version:
v5

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:
python 3.7

Repro steps:
setup-python python-version: 3.7

Expected behavior:
python 3.7 installs and works

Actual behavior:

Run actions/setup-python@v5
  with:
    python-version: 3.7.16
    check-latest: false
    token: ***
    update-environment: true
    allow-prereleases: false
Installed versions
  Version 3.7.16 was not found in the local cache
  Error: The version '3.7.16' 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

Activity

  1. jvesely
    added
    bugSomething isn't working
    needs triage
    on Apr 26, 2024
  2. jvesely
    added 4 commits that reference this issue on Apr 26, 2024

    ci/docs: Use default python-architecture to build docs

    51e4d65

    ci/docs: Use default python-architecture to build docs

    fa66f21

    ci/docs: Use default python-architecture for each platform to build docs

    d4b33f0

    ci/ga/docs: Use default python-architecture for each platform to buil…

    84f0a7a

  3. shawnbrown commented on Apr 27, 2024

    @shawnbrown
    shawnbrown
    on Apr 27, 2024

    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

  4. woodruffw commented on Apr 28, 2024

    @woodruffw
    woodruffw
    on Apr 28, 2024

    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).

  5. v-aparnajyothi-y
    removed
    needs triage
    on Apr 29, 2024

  6. v-aparnajyothi-y commented on Apr 29, 2024

    @v-aparnajyothi-y
    v-aparnajyothi-y
    on Apr 29, 2024
    Contributor

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

  7. mayeut commented on Apr 29, 2024

    @mayeut
    mayeut
    on Apr 29, 2024
    Contributor

    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

  8. mikedh commented on Apr 29, 2024

    @mikedh
    mikedh
    on Apr 29, 2024

    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.

  9. woodruffw commented on Apr 29, 2024

    @woodruffw
    woodruffw
    on Apr 29, 2024

    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.)

  10. jvesely commented on Apr 29, 2024

    @jvesely
    jvesely
    on Apr 29, 2024
    Author

    (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

  11. cclauss commented on Apr 30, 2024

    @cclauss
    cclauss
    on Apr 30, 2024
    Contributor

    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)

  12. cclauss commented on May 4, 2024

    @cclauss
    cclauss
    on May 4, 2024
    Contributor

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

    This is why I created the workaround:

    @mikhailkoliada

  13. jherland
    added 3 commits that reference this issue on May 6, 2024

    CI: Skip tests on v3.7/macos: GH lacks Python v3.7 on ARM-based macos

    b44b681

    CI: Skip tests on v3.7/macos: GH lacks Python v3.7 on ARM-based macos

    fa52123

    CI: Skip tests on v3.7/macos: GH lacks Python v3.7 on ARM-based macos

    218ce92

  14. henryiii commented on May 9, 2024

    @henryiii
    henryiii
    on May 9, 2024

    No, the first version of Python to support Apple Silicon was 3.8. That just barely supported ARM, as it was hitting the 1.5 year support window for new features as Apple Silicon came out (which is also when official binaries stop being built). 3.9 has much better support. Older versions do not support Apple Silicon1.

    3.7 is technically EOL, but many core Python tools (like pip itself) have an compatibility policy that includes 3.7.

    The next release of pip (24.1b1) drops support for 3.7. Most other PyPA packages have dropped support for running on 3.7 (build, packaging, hatch, flit, setuptools, twine, wheel, pipx, setuptools_scm, cibuildwheel, installer, auditwheel, distutils). The only PyPA tools I'm aware of that still support running on 3.7 are pyproject-metadata (because I haven't dropped it yet 😳) and virtualenv.

    I'd be nice if that was the default for setup-python

    I would never want the default for Apple Silicon to be Intel emulation! It's nice if we have it as an option (if it worked), but trying to use it by default would cause issues (including potentially miscomputed binaries) as well as would be a terrible default in the future when Intel Apple machines are a memory.

    Footnotes

    1. Apple briefly provided a patched 2.7 that they stopped shipping in macOS 12.3. And Xcode-command-line-tools Python 3.8 has their own patches. ↩

  15. cclauss commented on May 9, 2024

    @cclauss
    cclauss
    on May 9, 2024
    Contributor

    @jvesely I think this issue can be closed as won’t do.

  16. danibene
    added a commit that references this issue on May 12, 2024

    only test python 3.8

    5589d4a
  17. v-aparnajyothi-y
    self-assigned this
    on May 15, 2024

  18. jvesely commented on May 29, 2024

    @jvesely
    jvesely
    on May 29, 2024
    Author

    @jvesely I think this issue can be closed as won’t do.

    agreed. Thanks everyone!

  19. jvesely
    closed this as completedon May 29, 2024
  20. webknjaz
    added a commit that references this issue on May 30, 2024

    Run Python 3.7 tests on older macOS 13

    a7c0815
  21. ajyoon
    added a commit that references this issue on Jun 15, 2024

    Pin build macos to 13

    18db5c2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions