Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Provide x64, arm64, and universal2 arch selectors for darwin
See original GitHub issueDescription: Describe your proposal.
As described in this comment by @misl6, it would be nice to add the possibility to choose between arch = universal2, arm64, x64 on darwin (macos).
Justification: Justification or a use case for your proposal.
Runners for arm64 macos are in the github roadmap, but are not generally available. Once they are, it would be nice to be able to use either “thin” (x86_64 or arm64) or universal2 pythons on that image. Some work toward this was done in PR #114 which was merged then reverted. The design for the arch selector should already be worked out before making the images available:
- what is the exact syntax of the selector
- what will the default be
Note that PyPy is going to release both thin arm64 and x86_64 binary packages in its next release, and CPython already has a universal2 package.
I would propose supporting all three alternatives, as the scientific python stack (NumPy, SciPy, and more) and conda-forge have decided to support thin binary packaging only. It would be convenient if this action would make it easy to support those decisions by not forcing a universal2-only solution.
xref issue #108 which discusses the need for arm/arm64 python.
Are you willing to submit a PR?
Yes, but I don’t know if it is relevant for an outside contribution.
Issue Analytics
- State:
- Created 10 months ago
- Reactions:3
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
+1 To this. I’m building an Ubuntu 22.04 runner on ARM64 from the runner-images repo and the lack of ARM64 toolcache packages makes it impossible to use this action. TBH all the “setup/xxx” toolcache packages should be multi-arch.
The link you posted states that “self-hosted runners are available”. That is great, and is probably enough to justify formalizing the syntax for the selectors now. I was relating to the possibility of github-hosted runners, which seems to be not generally available yet.