-
Notifications
You must be signed in to change notification settings - Fork 15
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
Windows GHA #108
Windows GHA #108
Conversation
It looks like the definition for The macOS 12.7.4 runners apparently had pre-installed binaries for Python 3.7 through 3.12, the Python setup action did not have to check the versions manifest (https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json) to find suitable downloads. The macOS 14.4.1 runner only has Python 3.11 and up pre-installed, all older versions are downloaded and built with data from the Python versions manifest. This version manifest shows no arm64 Python 3.7 build. A solution could be to force the older macOS runner for Python 3.7 or drop building wheels and testing for Python 3.7 on macOS. |
Maybe it is time to drop support for Python 3.7, as it has reached its end of life at 2023-06-27. |
@dataflake But for now it seems to be easier to fix it like you suggested. We have to many open issues to also add dropping 3.7 support right now. |
Can you remind me since this |
@dataflake I am using zopefoundation/meta#207 here and my current goal is to make it ready to be merged. |
OK, I'll add the changes there and run it against this package again |
With the change in zopefoundation/meta@c0bfa85 the build and test runs again. When this is merged the branch protection rule for |
No description provided.