Summary

Update unit tests for the latest setuptools dependency updates.

Review Request #15102 — Created June 7, 2026 and discarded June 10, 2026, 12:05 a.m.

Information

Owner

chipx86

Repository

buildthings

Branch

master

Bugs

Depends On

Reviewers

Groups

beanbag-misc

People

Description

Setuptools now includes wheel as a dependency for editable installs

and isolated build environments, which the unit tests weren't checking

for. This is now included in the appropriate tests.
It also changed how dependency version specifiers are represented.

Instead of package>=1.0, it's now package >=1.0, with a space after

the package. This affected some tests as well, though doesn't impact

anything at package time.
To match this, the setuptools dependency has been bumped to the latest

major releaase. In a build environment, this will effectively always

be the case, but now we're explicit about it and will have it in unit

tests.

Testing Done

All unit tests pass.

Commits

Summary	ID
Update unit tests for the latest setuptools dependency updates. Setuptools now includes `wheel` as a dependency for editable installs and isolated build environments, which the unit tests weren't checking for. This is now included in the appropriate tests. It also changed how dependency version specifiers are represented. Instead of `package>=1.0`, it's now `package >=1.0`, with a space after the package. This affected some tests as well, though doesn't impact anything at package time. To match this, the `setuptools` dependency has been bumped to the latest major releaase. In a build environment, this will effectively always be the case, but now we're explicit about it and will have it in unit tests.	5719ec5f227aa5afa59d4ac3cec0480d71f5567e

Summary

Update unit tests for the latest setuptools dependency updates.

Setuptools now includes `wheel` as a dependency for editable installs and isolated build environments, which the unit tests weren't checking for. This is now included in the appropriate tests. It also changed how dependency version specifiers are represented. Instead of `package>=1.0`, it's now `package >=1.0`, with a space after the package. This affected some tests as well, though doesn't impact anything at package time. To match this, the `setuptools` dependency has been bumped to the latest major releaase. In a build environment, this will effectively always be the case, but now we're explicit about it and will have it in unit tests.

5719ec5f227aa5afa59d4ac3cec0480d71f5567e

Issues

Description	From	Last Updated
Should we pin setuptools>=80 to match this behavior, at least in dev-requirements.txt?	david	June 9, 2026, 11:27 p.m.

flake8 passed.

JSHint passed.

The issue has been resolved. Show all issues

Should we pin setuptools>=80 to match this behavior, at least in dev-requirements.txt?

chipx86

June 9, 2026, 11:12 p.m.

I was trying to figure out what to do here, but I think since this is a build-time dependency and it's always going to get the latest version at build time, there's no point in limiting to dev-requirements.txt. We're right now just setuptools==latest. Given that, I'll just bump to the latest major.

Change Summary:

Updated the setuptools dependency to >= 82.

Description:

		Setuptools now includes `wheel` as a dependency for editable installs
		and isolated build environments, which the unit tests weren't checking
		for. This is now included in the appropriate tests.

		It also changed how dependency version specifiers are represented.
		Instead of `package>=1.0`, it's now `package >=1.0`, with a space after
		the package. This affected some tests as well, though doesn't impact
		anything at package time.
	+
	+	To match this, the `setuptools` dependency has been bumped to the latest
	+	major releaase. In a build environment, this will effectively always
	+	be the case, but now we're explicit about it and will have it in unit
	+	tests.

Commits:

	Summary	ID
	Update unit tests for the latest setuptools dependency updates. Setuptools now includes `wheel` as a dependency for editable installs and isolated build environments, which the unit tests weren't checking for. This is now included in the appropriate tests. It also changed how dependency version specifiers are represented. Instead of `package>=1.0`, it's now `package >=1.0`, with a space after the package. This affected some tests as well, though doesn't impact anything at package time.	398300f75270c89a437973274d2de6428e65f6e2
	Update unit tests for the latest setuptools dependency updates. Setuptools now includes `wheel` as a dependency for editable installs and isolated build environments, which the unit tests weren't checking for. This is now included in the appropriate tests. It also changed how dependency version specifiers are represented. Instead of `package>=1.0`, it's now `package >=1.0`, with a space after the package. This affected some tests as well, though doesn't impact anything at package time. To match this, the `setuptools` dependency has been bumped to the latest major releaase. In a build environment, this will effectively always be the case, but now we're explicit about it and will have it in unit tests.	5719ec5f227aa5afa59d4ac3cec0480d71f5567e

Diff:

Revision 2 (+66 -42)

Show changes

	pyproject.toml
	buildthings/tests/test_backend.py

Checks run (2 succeeded)

flake8 passed.

JSHint passed.

Status:: Discarded
Change Summary:: I think this was ultimately environmental. These updates fail on a brand-new environment on all Python versions.