Help pip to find appropriate boto for aiobotocore #49166
Merged
Conversation
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
Seems that `pip` has troubles with finding the right boto3 for aiobotocore which results in resolution too deep when trying higher versions of boto3 than aiobotocore supports. This limit should come from the aibotocore[boto3] extra, but apparently `pip` does not use it straight away to limit boto3, instaead it attempts to find resolution for higher versions of boto3 and discard it later with aiobotocore. We pin the latest aiobotocore - this way in the future when we enable dependabot, we will be able to upgrade aiobotocore together with updating the limits for botocore.
boring-cyborg
bot
added
area:providers
provider:amazon
ashb
approved these changes
Apr 12, 2025
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.
Seems that
piphas troubles with finding the right boto3 for aiobotocore which results in resolution too deep when trying higher versions of boto3 than aiobotocore supports.This limit should come from the aibotocore[boto3] extra, but apparently
pipdoes not use it straight away to limit boto3, instaead it attempts to find resolution for higher versions of boto3 and discard it later with aiobotocore.We pin the latest aiobotocore - this way in the future when we enable dependabot, we will be able to upgrade aiobotocore together with updating the limits for botocore.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.