Set a lower bound on aiohttp dependency

[TomNicholas]

Currently s3fs's aiohttp requirement has no lower bound:

aiohttp!=4.0.0a0, !=4.0.0a1

This means that dependency resolvers using lowest-version resolution (e.g. uv --resolution lowest-direct) can resolve to ancient, broken versions of aiohttp (e.g. 0.1), which fail to build.

Would it be possible to add a lower bound, e.g. aiohttp>=3.9.0?

[martindurant]

Why would anyone do that?

ancient, broken versions of aiohttp

broken how?

[TomNicholas]

Why would anyone do that?

VirtualiZarr has a CI job to test against minimum-dependencies (as does xarray). I tried using re-implementing it using uv --resolution lowest-direct which broke when it got to s3fs.

broken how?

The lowest version of aoihttp only declares support for python 3.3 and 3.4. I can't even build that version of aoihttp.

Are you expecting s3fs to work with all versions of aoihttp, going back 4 major versions, back to 2014? Surely s3fs should specify a lower bound somewhere?

[TomNicholas]

I mean maybe this is a silly thing for me to try but I do wonder if s3fs should specify the minimum version of dependencies you explicitly support, even if its an arbitrary choice.

[martindurant]

--resolution lowest-direct seems like something you might want on your own deps, not the deps of those deps. Anyway - happy to have some minimum, it is reasonable, but will take some digging. Say, two years old would be fine.