Closed jasonamyers closed 4 years ago
we have extras for boto3 + awscli, you should use those. So your req should be aiobotocore[boto3]
. re-open if there's something I missed. The tight coupling is just the nature of this beast given how tightly we are coupled with botocore.
Describe the bug I'm having a hard time installing aiobotocore beside many of our common tools due to older botocore requirements.
Could not find a version that matches botocore<1.13.15,<1.15.0,>=1.13.14,>=1.14.9
Checklist
pip check
passes without errorspip freeze
resultspip freeze results aiobotocore==0.11.1 aiohttp==3.6.2 alembic==1.3.3 async-generator==1.10 async-timeout==3.0.1 attrs==19.3.0 boto3==1.11.9 botocore==1.14.9 cffi==1.13.2 chardet==3.0.4 credstash==1.16.1 cryptography==2.8 dnspython==1.16.0 docutils==0.15.2 idna==2.8 jmespath==0.9.4 Mako==1.1.1 MarkupSafe==1.1.1 mixpanel==4.5.0 multidict==4.7.4 mysql-connector-python==8.0.19 protobuf==3.6.1 pycparser==2.19 python-dateutil==2.8.0 python-editor==1.0.4 python-json-logger==0.1.11 PyYAML==5.3 s3transfer==0.3.2 six==1.14.0 SQLAlchemy==1.3.13 urllib3==1.25.8 wrapt==1.11.2 yarl==1.4.2
Environment:
Additional context Here is a Pipenv graph. You can see that aiobotocore and credstash for example can not live together peacefully, nor can current boto3 and several other AWS libs we use that rely on a higher version of botocore.