chore: Remove py37 support, and unify compatibility matrix from 3.8-3.9 #2226
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Remove python 3.7 support since it has reached its EOL, and unify the compatibility matrix across services to include 3.8 and 3.9
Motivation and Context
We are going to be upgrading our services to py3.10 soon, so this is getting the project set up for that. py3.10 won't be added in this PR yet because it appears to require other package upgrades, so keeping the focus on removing py3.7 here. We will need to upgrade flask and werkzeug with our py3.10 upgrade, and werkzeug 3.0.1 does not support py3.7 so that is the main motivation.
How Has This Been Tested?
Documentation
Updated all relevant docs that show version requirements
CheckList