Repository navigation
Conversation
| {%- for v in pys[1:] %} | ||
| - linux: py{{ v | replace('.', '') }} | ||
| {%- endfor %} | ||
| - windows: py{{ pys | first | replace('.', '') }} | ||
| - macos: py{{ pys[1] | replace('.', '') }} | ||
| - linux: py{{ pys | first | replace('.', '') }}-oldestdeps | ||
| - linux: py{{ pys | last | replace('.', '') }}-devdeps |
There was a problem hiding this comment.
It turns out it was reasonably hard to encode my gut instinct about what the [platform, version] matrix should be in jinja code.
As currently written we test the two oldest pythons on windows & macos and the newer ones on linux. Given the SPEC 0 rotation we should generally have 3 or maybe 4 supported Pythons. I think the latest one should be linux as it's more likely to work [compile quickly] when a version is very new.
There was a problem hiding this comment.
I think this actually makes it clearer what combinations run, I think it could be doc'd quickly the specific combinations we run.
| - linux: py313 | ||
| - linux: py{{ default_python | replace('.', '') }} |
There was a problem hiding this comment.
this job is ran again below in test?
There was a problem hiding this comment.
To be clear, don't think I care.
PR Description
This should allow us to add or remove supported Pythons and have most places update.
This replaces the old
minimum_supported_pythonwith a list of supported python versions, which is then used in various places to generate tox envs, default pythons (normally the second to newest), wheel versions etc.AI Assistance Disclosure
AI tools were used for: