[client-python] Loosen boto3 version constraint to fix stix-shifter compatibility (#14613)#14692
Conversation
|
Thank you for your contribution, but we need you to sign your commits. Please see https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #14692 +/- ##
=======================================
Coverage 32.36% 32.36%
=======================================
Files 3097 3097
Lines 210978 210978
Branches 38230 38230
=======================================
Hits 68280 68280
Misses 142698 142698
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
jabesq
left a comment
There was a problem hiding this comment.
LGTM 👍
Please sign all your commits using the following commands while on the claude/fix-boto3-requirements-issue branch, before merging it into master:
git rebase origin/master -x "git commit -S --amend --no-edit"
…ompatibility Co-authored-by: SamuelHassine <1334279+SamuelHassine@users.noreply.github.com>
4dfe0c9 to
3a2b478
Compare
|
Please attach at least one issue to your Pull Request |
1 similar comment
|
Please attach at least one issue to your Pull Request |
The strict
boto3~=1.38.27constraint prevents pip from resolving dependencies when connectors install bothpyctiandstix-shifter(which depends onaiobotocorewith strictbotocore<1.38.28requirements).Changes
boto3~=1.38.27→boto3>=1.38.27,<1.44boto3~=1.38.27→boto3>=1.38.27,<1.44The wider range allows pip to select compatible boto3/botocore versions based on the full dependency graph:
Example error before fix:
Original prompt