Closed JackKolb-ElationHealth closed 11 months ago
Thinking this through, I think we might need a dep bump in aiobotocore, not botocore. I added a comment to a existing PR to bump the version of botocore within aiobotocore: https://github.com/aio-libs/aiobotocore/pull/1037#issuecomment-1752108437
But I think we may need a version bump here for aiobotocore once it releases.
Yeah once a aiobotocore update is out, i'll update this.
Looks like aiobotocore 2.7.0 is out, which pins botocore to botocore>=1.31.16,<1.31.65
🎉
Would it be a version bump or does it require wrapping new async codepaths?
I'd assume aiobotocore took care of that but I'm not too familiar with it
Would it be a version bump or does it require wrapping new async codepaths?
I'd assume aiobotocore took care of that but I'm not too familiar with it
There were no new async codepaths, merely a version bump. That should all be taken care of in aiobotocore==2.7.0
.
Sorry about the delay, v12.0.0 is out.
Description
I'm creating a AWS bedrock microservice that uses async boto for nonblocking requests/responses. This microservice is calling AWS bedrock, a relatively new service that provides developer access to LLMs like Claude.
What I Did In Boto3
What I Did In AIOBoto3
The error :
I believe this is due to the current dep version of botocore being a bit older.
I'm naively suggesting a bump to the version of botocore, but I'm not sure how big of a lift that would be.
Let me know if I can provide any more details, happy to help however.