[solved] Did anyone here encounter a conflict between

boto3

(AWS python API) (including

botocore

and

aibotocore

) and

s3fs

that

kedro-datasets

rely upon? Is there another version of

kedro-dataset

that replaces

s3fs

with

aibotocore

to fix this conflict?

Hi @Artur Dobrogowski what's the issue you're facing? We recently bumped

s3fs

, because we were on a super outdated version (https://github.com/kedro-org/kedro-plugins/pull/463).

I'm told by poetry:

And because kedro-datasets (2.0.0) depends on s3fs (>=2021.4,<2024.1)
 and no versions of kedro-datasets match >2.0.0,<3.0.0, boto3 (>=1.34.19,<2.0.0) is incompatible with kedro-datasets (>=2.0.0,<3.0.0).

I think this sums this up well: https://stackoverflow.com/questions/75743038/resolving-dependencies-fails-on-boto3-and-s3fs-using-poetry

No worries!