-
Notifications
You must be signed in to change notification settings - Fork 16
Remove macos-13 #299
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
Remove macos-13 #299
Conversation
# if Python is <3.10 we can't use macos-latest which is arm64 | ||
try: | ||
if Version(item["python_version"]) < Version('3.10') and item["os"] == "macos-latest": | ||
item["os"] = "macos-13" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about not removing this for a while, but actually I think removing it and having the error be "can't find Python 3.9" is better than "huh what why is this on macos-13".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But 3.9 is still available on macos-14, right? (or rather, added in actions/runner-images#9813)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, forgot again that that is the macos-large
version. But then there won't actually be a free version available with Python < '3.11'
anymore, unless I am missing something? Or they are yet adding it to macos-14 and/or -15; support policy indicates that 3.10 should still be available after 3.14 is out, though it does not explicitly guarantee this for all platforms...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤷 lol
@@ -60,13 +60,6 @@ To not build any wheels: | |||
targets: '' | |||
|
|||
For additional configuration extra arguments can be passed by making a target a dictionary. | |||
An example of this is specifying the runner for a target, such as building macos x86_64 wheels on native x86_64 runners: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anyone got an idea of an example here which would still work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor suggestion, otherwise LGTM
|
||
targets: | ||
- target: cp311-macosx_x86_64 | ||
runs-on: macos-13 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to swap out the example instead of removing it altogether?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Preferably
The bigger issue I think is the arm non-arm switch, and that's what we run into regarding this upgrade for pytest-arraydiff (I mean the bug is downstream as the tests should handle the missing dependency, yet here we are): astropy/pytest-arraydiff#55 |
Fixes #298