You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we lingered at a non-latest version of python for quite a while, I think it makes sense to move to v3.12 given that it came out on August 21, 2023.
Given that we are relying a handful of outside things for development (GitHub action machines, etc.), it may be best to try this in a month or so.
The text was updated successfully, but these errors were encountered:
## Fixes issue
#1031
## Description of Changes
Update 🐍 version matrix to include `3.12`. At some point I'd like to
move the application to `3.12`, but I think now isn't the time.
## Tests and linting
- [x] This branch is up-to-date with the `develop` branch.
- [x] `pytest` passes on my local development environment.
- [x] `pre-commit` passes on my local development environment.
What issue are you seeing?
Since we lingered at a non-latest version of python for quite a while, I think it makes sense to move to
v3.12
given that it came out on August 21, 2023.Given that we are relying a handful of outside things for development (GitHub action machines, etc.), it may be best to try this in a month or so.
The text was updated successfully, but these errors were encountered: