Use isolated build environments

[cdce8p]

Proposed change

PEP 517 added the option to specify build backends via pyproject.toml. The build package is then used to create isolated build environments. This helps ensure that the all builds are reproducible. E.g. in the past it was possible that the build was tested with one version of setuptools while the final release was done with another (older) one which didn't work as expected.

https://setuptools.pypa.io/en/latest/build_meta.html

The change will also allow us to eventually remove setup.py completely.

/CC @balloob

The deprecation warning is a result of pip 21.2 and can be ignore. It will disappear with 21.3.x.

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)
• 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 #
• 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
• The code has been formatted using Black (black --fast 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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[frenck]

We actually don't use this script for releasing...

core/.github/workflows/builder.yml

Lines 76 to 80 in 956ceb6

	- name: Build package
	shell: bash
	run: |
	pip install twine wheel
	python setup.py sdist bdist_wheel

[cdce8p]

Thanks! Updated that too. I'm not entirely sure which workflow Github will choose once this is merged, the old or new one (for the 2022.1 release).

To be safe, it might make sense to cherry-pick the prerequisite PRs:

• Move version metadata key to setup.cfg #65091
• Move install_requires to setup.cfg #65095
• Move project_urls to setup.cfg #65129

[frenck]

As far as I am aware (thus not 100% certain), it will use the default branch, which is dev

[balloob]

Let's remove script/release

[cdce8p]

As far as I am aware (thus not 100% certain), it will use the default branch, which is dev

That's what I remember as well. In that case, the three merged PRs above and this one should be cherry-picked if accepted.

[cdce8p]

Let's remove script/release

👍🏻 Done

[frenck]

@balloob This means we need to tag this and the other listed above for the milestone.
Do we want this in the current beta path?