Pinning for aiobotocore dependency (s3 remote) is too strict.

As of dvc==2.5.4 (holds for older versions as well), setup.py pins aiobotocore[boto3]==1.3.0 for s3 remote use. Such a strict pinning of aiobotocore results in an equally strict pinning of botocore (which is quite natural for an adapter library). The direct consequence is that having both dvc[s3] and boto3 in the same requirements.in makes it impossible to compile most of the time (at least until pip-tools gets a better resolver implemented). Would it be conceivable to release a bit the constraint on the aiobotocore[boto3] version pinning?

[hugo-ricateau]

Thanks for this fast answer. Waiting until next week is a reasonable option.

[isidentical]

Since we use both aiobotocore and boto3, it is really important to make them both compatible. I don’t recall any particular problem that was related to aiobotocore version so we might relax it a bit (>1.0.1 instead ==1.3.0) and see where it goes.