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
Python 3.8 is no longer getting security updates, so we'll be dropping support. It's likely that things will continue to work for some time, but we'll stop running tests and will be removing linter workarounds and pyupgrade stuff.
Todo list:
remove python 3.8 from testing.yml
remove any package workarounds that reference python 3.8 (there's some in dev-requirements.txt for sure)
change configuration for pyupgrade in .pre-commit-config.yaml
look through code to see if we have other python 3.8 specific workarounds that should be flagged for eventual removal (can set up separate issues for these if we don't want to pull them out right away). There might be a couple in the tests specifically.
This should be pretty easy to do, the only reason I'm not flagging it as a good first issue is that I'm going to be swamped this week so I won't have time to walk someone through it beyond what's written here. Anyone should feel welcome to pick this up OR speak now on this issue if you absolutely need us to keep 3.8 support a bit longer.
The text was updated successfully, but these errors were encountered:
terriko
changed the title
ci: remove python 3.8 from officially supprorted
ci: remove python 3.8 support
Nov 19, 2024
Python 3.8 is no longer getting security updates, so we'll be dropping support. It's likely that things will continue to work for some time, but we'll stop running tests and will be removing linter workarounds and pyupgrade stuff.
Todo list:
This should be pretty easy to do, the only reason I'm not flagging it as a good first issue is that I'm going to be swamped this week so I won't have time to walk someone through it beyond what's written here. Anyone should feel welcome to pick this up OR speak now on this issue if you absolutely need us to keep 3.8 support a bit longer.
The text was updated successfully, but these errors were encountered: