Remove `awscli` and `boto3` optional dependencies

[jakob-keller]

We currently support and advertise installing aiobotocore along with supported versions of awscli and boto3 using optional dependencies:

pip install -U 'aiobotocore[awscli,boto3]'

I view this primarily as a historic legacy and propose to remove those optional dependencies on the following grounds:

• modern pip and equivalent tools (uv, poetry, ?) should be fully capable of resolving the dependency graph and installing compatible sets of dependencies by merely running pip install -U aiobotocore awscli boto3 or equivalent. I am unaware of any need for those optional dependencies.
• awscli is pinning to 1.x releases of the AWS CLI. AWS CLI 2.x has been around for years. AWS CLI 1.x might not be relevant anymore for the majority of users.
• The awscli extra is not beening tested as part of the development lifecycle, AFAIK.
• Keeping those extra dependency pins aligned with the pin on botocore is a recurring, manual task that complicates the process of bumping the supported botocore version range.

Any thoughts from users and maintainers?

If we reach consensus on this proposal, I would be happy to prepare a PR to include the change in the upcoming 3.0.0 release.

[jakob-keller]

@thehesiod, @webknjaz: I would love to hear your thoughts!

[webknjaz]

I don't know the history of this decision but it's possible that metadata might not sufficiently represent API-level compatibility between the deps.

[jakob-keller]

I don't know the history of this decision

#273 and #324 added the awscli and boto3 optional dependencies respectively in 2017.

[jakob-keller]

it's possible that metadata might not sufficiently represent API-level compatibility between the deps.

This codebase does not use or reference awscli or boto3 in any way, except for providing, documenting and testing the optional dependencies of the same name. To the best of my knowledge, those optional dependencies were introduced as mere affordances to work around past limitations of pip.

[webknjaz]

I suppose it's your call, then. If something isn't invoked directly, it shouldn't be in the direct deps..

[jakob-keller]

As a first step, I have prepared #1435 to remove the awscli packaging extra. Once this is merged, I intend to follow up with the removal of the boto3 packaging extra.

[jakob-keller]

I have prepared #1440 to remove the boto3 packaging extra and close this issue.

[thehesiod]

that's true, with uv the situation is much better. originally I think we added it because pipenv would take ages to lock or just fail to find a solution

[thehesiod]

btw sorry for some reason missed the notification on this