chore(api,shared-data): Require Python >=3.10, not >=3.8 #14867
Merged
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.
Overview
Closes EXEC-391.
Test Plan
Not sure. Is there a way to do something like a private PyPI deploy to test this?
Changelog
CLASSIFIERS
. As far as I know, these are just human-readable tags, and don't have any behavioral effect.python_requires
from>=3.8
to>=3.10
forapi
andshared-data
.Mercifully, I think we can do this without having to do another
pipenv lock
, which would conflict #14805.pipenv verify
doesn't complain.Review requests
Other than
api
andshared-data
, are there any other user-facing projects that this needs to happen in?Risk assessment
Low.