Backport to Python 3.9

[snoack]

No description provided.

[robbinjanssen]

@snoack what is the reason you still would like support for python 3.9 and 3.10? :)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (b897729) to head (61491c2).
Report is 22 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #231   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines          353       354    +1     
  Branches        55        55           
=========================================
+ Hits           353       354    +1     

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

[snoack]

In my case specifically, I'd like to use this library on Debian Bullseye which come with no newer than Python 3.9.

[robbinjanssen]

Cool, how do you use the package there? Did you build a simple app on top of it?

I think I want to keep the main branch python = "^3.11", however I'm open for a python-39 branch (and tag them as such), the problem is that it wont receive (regularly) dependency updates. Is that okay for you?

[snoack]

I was hoping to just install the package from PyPI once this PR has been merged and released. FWIW, this is the first package I came across that no longer supports Python 3.9.

I'd understand if supporting older Python versions would impair the code quality, maintainability, performance, or features as you cannot use more modern Python features. But I don't see this being the case here. All it would take to support Python 3.9 here would be:

• Using datetime.timezome.utc instead of datetime.UTC.
• Using asyncio.TimeoutError instead TimeoutError
• Importing Self from typing_extensions instead of typing.

In fact it seems less of a maintenance burden to just merge those changes into the main branch than maintaining a separate branch for Python 3.9 support. But it's your call.

[robbinjanssen]

I understand your reasoning, and mostly agree. I just created this library for my Home Assistant integration and it no longer uses python 3.9, thats why I bumped 😀

I'll merge this PR and release it!👍🏻

[robbinjanssen]

@snoack whoops, can you maybe update from main and fix/commit the lock file?

[snoack]

Done.

[robbinjanssen]

Thanks! Tagged as v3.1.1 :)