Add aiofiles to package constraints

[silamon]

Proposed change

Some (popular) custom integration https://github.com/UI-Lovelace-Minimalist/UI pinned aiofiles to 0.8.0, which has no support for python 3.12. Adding this library to package constraints as a temporary workaround. See #126904 for more information. There are 8 core integrations that rely on this library.

PR at the custom integration: UI-Lovelace-Minimalist/UI#1543

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes Linkplay, cannot set up Wiim Pro Plus - AttributeError: '_io.TextIOWrapper' object has no attribute 'delete' #126904
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[autinerd]

Please run the gen_requirements_all script.

[cdce8p]

Instead of adding a new constraint, couldn't we just add the custom integration to the block list here?

core/homeassistant/loader.py

Lines 92 to 94 in 4721f8e

	BLOCKED_CUSTOM_INTEGRATIONS: dict[str, BlockedIntegration] = {
	# Added in 2024.3.0 because of https://github.com/home-assistant/core/issues/112464
	"start_time": BlockedIntegration(AwesomeVersion("1.1.7"), "breaks Home Assistant"),

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[silamon]

Instead of adding a new constraint, couldn't we just add the custom integration to the block list here?

core/homeassistant/loader.py

Lines 92 to 94 in 4721f8e

	BLOCKED_CUSTOM_INTEGRATIONS: dict[str, BlockedIntegration] = {
	# Added in 2024.3.0 because of https://github.com/home-assistant/core/issues/112464
	"start_time": BlockedIntegration(AwesomeVersion("1.1.7"), "breaks Home Assistant"),

It doesn't crash or cause any performance issues atm. I don't think it's right to take out the bazooka for this one.

[cdce8p]

It doesn't crash or cause any performance issues atm. I don't think it's right to take out the bazooka for this one.

But isn't the result similar? With either method the custom integration will fail to install. Either because of the check for blocked integrations or because the requirements don't match our constraints. Better to have a good error message then.

[silamon]

I'm going to close this one, since I don't think it appropriate to block a custom integration at this moment.