🏷️ chore: drop Python 3.9 classifier#235
Open
YashGaykar0309 wants to merge 1 commit into
Open
Conversation
Remove the Python 3.9 package classifier because the SDK requires Python 3.10 or newer.
YashGaykar0309
had a problem deploying
to
eu-west-2
GitHub Actions
Failure
YashGaykar0309
had a problem deploying
to
eu-west-2
GitHub Actions
Failure
jobs62
approved these changes
Jun 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Remove the Python 3.9 package classifier because the SDK requires Python 3.10 or newer.
Description
Remove the Python 3.9 package classifier from pyproject.toml to align the advertised supported Python versions with the SDK requirement of Python 3.10 or newer.
This change makes the package metadata consistent and avoids suggesting Python 3.9 compatibility when it is not supported.
Type of Change
Please check the relevant option(s):
How Has This Been Tested?
Please describe the test strategy:
Checklist