ci: Restrict python versions differently #8453
Conversation
12d1df4 to
1f9f318
Compare
I could be reading the change wrong but doesn't this change still restrict the version of Python?
By removing the line that specifies |
This is mostly referring to the fact that Python for the macOS runner was specifically restricted to version 3.12.2, while in other cases it was 3.x. It's true that in general I changed the default to be 3.13.x, but the decision here is to get bugfixes but not versions that can break things, if we are not ready to handle them.
If you check the CI it's actually defaulting to arm64. It's indeed a bit confusing because leaving the default for the macOS-12 runner, it choose the I'll add back the architecture but with |
|
That's what I get for trusting documentation! :-P Edit: I've opened an issue on their repo actions/setup-python#966 |
d074025 to
982a844
Compare
- Change the installed version to 3.13.x - Don't restrict to a single version on macOS, but let newer minor versions be installed - Don't use x64 python on macOS arm runners - Fix python binary substitution in the test files when builder architecture doesn't correspond with tester architecture. - Use a sed separator that doesn't create problems with BSD sed, and isn't a regex operator - Correct the in place option usage if the package_tests.sh is ever used with BSD sed, since it doesn't work the same as GNU sed
982a844 to
51813fb
Compare
doesn't correspond with tester architecture.
since it doesn't work the same as GNU sed