Adjust aiohttp pin

[cdce8p]

Update aiohttp pin to allow versions other then 3.8.x with <4.

Background: It looks like aiohttp will add support for Python 3.12 only in 3.9.0. By pinning <3.9 this packages unnecessarily constraints what versions downstream packages or apps can install. With semantic versioning everything up to <4.0 should be backwards compatible.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (f7fcaf6) 100.00% compared to head (6ba05de) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #425   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           27        27           
  Lines         2388      2388           
=========================================
  Hits          2388      2388           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[leszekhanusz]

The 3.9 aiohttp version is not released yet, but they sure are supposed to follow semver so we might allow it.

But why did you want this change now before the version is available? Why not wait that the 3.9 version is available and verify that all the tests are working before doing this change?

[cdce8p]

The 3.9 aiohttp version is not released yet, but they sure are supposed to follow semver so we might allow it.

But why did you want this change now before the version is available? Why not wait that the 3.9 version is available and verify that all the tests are working before doing this change?

I've already starting testing Python 3.12 for Home Assistant. Since we have a lot (>880) direct dependencies, it's quite common that a new Python version doesn't work initially. The earlier we can fix potential issues, the easier it will be to fully support it later on once 3.12 is released.

Just for reference, this is the aiohttp PR aio-libs/aiohttp#7400 which added build support for Python 3.12. It was only tagged to be backported to 3.9 not 3.8. That's why I already checked which of our dependencies aren't compatible.

[leszekhanusz]

This is now available in pre-release 3.5.0b5.