Allow using jmespath 1.x - #544
Merged
Merged
Conversation
|
|
|
@sdk-team can this be merged and released? This has been sitting here for almost a year. Related: |
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
5 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.
Relax the
aliyun-python-sdk-corerequirements to support jmespath 1.x and Python 3.11.With the changes in the
randompackage in Python 3.11, therandom.samplefunction now requires a sequence as its first argument. This issue has been addressed in jmespath with this PR: jmespath/jmespath.py#217.The usage of
jmespathin this SDK is straightforward and does not necessitate a 0.x version. Therefore, we can relax the constraint to allow 1.x versions as well to ensure broader SDK support for new Python versions.