-
-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove _register_lazy_block_unknown_fips_pseudo_regions #905
Comments
DetailsThe caller of aiobotocore is at the following location.
This corresponds to the following function in the parent class botocore.
In botocore 1.23.0 and later, the above line has been removed and the following line has been added in its place.
So I confirmed this issue was resolved by patching the following diff. Actually, according to the Contributing policy, it seems that aiobotocore needs to be updated entirely to match the version of botocore.
|
this is not an issue of removing this method, it's about ensuring the version of botocore matches the version required by aiobotocore per the req in setup.py. This is covered by #904 . The patch needs to batch all methods that are overridden per: https://github.com/aio-libs/aiobotocore/blob/master/CONTRIBUTING.rst#how-to-upgrade-botocore. closing this as it's much more involved than the diff mentioned above and is covered by #904 |
Ref: aio-libs/aiobotocore#905 (comment) git-svn-id: file:///srv/repos/svn-community/svn@1065594 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Ref: aio-libs/aiobotocore#905 (comment) git-svn-id: file:///srv/repos/svn-community/svn@1065594 9fca08f4-af9d-4005-b8df-a31f2cc04f65
I confirmed this error was resolved with aiobotocore 2.1.0. Thank you very much! |
@hayashier May I know which boto* and aio* versions are you using ? |
can you please post callstack? |
Sorry for opening the same issue(#900) again because I couldn't reopen that issue(only repo owner or collaborator can reopen as far as I know).
I investigated this issue and found this issue is caused by this change(boto/botocore#2558) in botocore 1.23.0.
aiobotocore 2.0.1 is tied to botocore 1.22.8. So in order to resolve this issue, I confirmed aiobotocore should bump to botocore 1.23.0 or later(For example, 1.23.14)
https://github.com/aio-libs/aiobotocore/blob/2.0.1/setup.py#L10
So I opened the issue(#904) which requests to bump to botocore 1.23.0 or later.
Thanks,
The text was updated successfully, but these errors were encountered: