You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Greetings! I'm reporting a recent regression in some tests I'm maintaining but didn't write myself. (Apologies if I'm missing some context, but I've tried to gather all the relevant information.)
The moto package has no integration with or awareness of aiobotocore, so it wouldn't even be possible for moto to return an AioAWSResponse object. If there is a genuine defect in moto behavior that breaks a third party library, we would try to remedy that, but I don't think that's the case here. In fact, a cursory search turned up this discussion. If you scroll to the bottom, it seems there are recent workarounds to get the versions of moto and aiobotocore you are using to play nice with each other.
ya my apologies I should have stated that aiobotocore is not supported, poor choice of words on my part. let's continue the discussion of workarounds on that other thread.
Greetings! I'm reporting a recent regression in some tests I'm maintaining but didn't write myself. (Apologies if I'm missing some context, but I've tried to gather all the relevant information.)
The following is a MWE due to @kjagiello:
repro.py
Run with
uv
:The result is
triggered by these lines.
According to aio-libs/aiobotocore#1320 (comment), this is a bug in moto because moto returns an AWSResponse instead of an AioAWSResponse. This bug was obscured in aiobotocore versions <2.21, but uncovered by the change in aio-libs/aiobotocore#1301.
The text was updated successfully, but these errors were encountered: