[BUG FIX] Only use the major.patch version to check deprecation status #11214
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.
What are you trying to accomplish?
Fix a bug where we compare a python version in major.minor.patch format against a list of python versions in major.minor format to check whether the version is deprecated. For example, 3.8.20 was coming up as not deprecated because we were comparing it against
[3.8]
. My solution is to only use the major.minor version to check deprecation status.How will you know you've accomplished your goal?
I'll see a language deprecation warning, in the logs, for a repo with a python version greater than 3.8 but less than 3.9
Checklist