Use a consistent Python version in CI actions #96
Description
Feature description
A couple of the different tasks have different ways of picking a specific Python version to use. We maybe want to make them all the same, or leave comments if there's a logic for why it's different.
Use case
Idk, it looks weird
Acceptance Criteria
- look at all places where actions/setup-python is using a specific python version, and either make them all resolve to the same version (e.g.
3.x) or justify exceptions
Proposed solution
No response
Alternatives considered
No response
Implementation details
No response
Potential Impact
No response
Additional context
No response
Contribution
None