-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide macOS Monterey and Ventura wheels #814
Comments
You do not need to build on the latest macOS. On macOS, you set MACOSX_DEPLOYMENT_TARGET to the oldest macOS you support, and the stdlib will only include binary components that support that version - or any newer version. So it's generally safe to upgrade to a newer macOS, but you do not need to. The only benefit is you might get access to newer header only changes (but this is C++11 IIRC, so unlikely to benefit). That's not the problem in that issue at all. Wheels list some version they target, then they work on all newer versions, following the way macOS works. Run |
Looks like 3.11 was missed here: iminuit/.github/workflows/release.yml Lines 40 to 48 in e636501
|
Ok, so all I have to do is to generate the missing wheel for Python3.11 then. |
Release 2.18.0 contains a Python3.11 wheel for macos universal2 |
If there are still issues, ping me and reopen. |
Confirmed availability w/ python 3.11 on Ventura. Thanks! |
As I'm sure you're aware the Github actions runner image
macos-latest
still points to Big Sur.macos-12
is the runner image for Monterey. Up-to-date wheels would be super helpful forpip
ing iniminuit
and prevent issues like #813.Unfortunately, as was unofficially announced just yesterday (actions/runner-images#6426 (comment)), the Ventura image won't be available until Q2. I can provide a Ventura self-hosted runner in the meantime.
The text was updated successfully, but these errors were encountered: