Summary

Switch Djblets package building to use buildthings.

Review Request #14952 — Created March 21, 2026 and submitted March 31, 2026, 9:44 p.m.

Information

Owner

chipx86

Repository

Djblets

Branch

release-5.x

Bugs

Depends On

Reviewers

Groups

djblets

People

Description

Buildthings is our new Python package build backend, which supports

injecting local development source trees into the isolated build

environment, interfacing with npm, and running extra build steps.

It also notably allows for local paths for development dependencies,

something our in-tree build backend did not do.
This change switches away from our in-tree build backend to

buildthings, giving us a consistent setup going forward and resolving

several issues when building Djblets.
When building Djblets, development and package dependencies will be

installed in the isolated build environment for all build types,

allowing static media to be built.
All build types support .local-packages, since we need this in order

to build and deploy in-development versions.
Builds can be tested using:
$ python -m build --sdist .
$ python -m build --wheel .

Doing these separately ensures that .local-packages will be picked up

for each build type, rather than the default behavior of the wheel being

built from the source distribution.

Testing Done

Tested editable installs and producing sdist and wheel builds.

Compared those to builds using the original build backend. Verified that
all files and metadata were a match.

Commits

Summary	ID
Switch Djblets package building to use buildthings. Buildthings is our new Python package build backend, which supports injecting local development source trees into the isolated build environment, interfacing with npm, and running extra build steps. It also notably allows for local paths for development dependencies, something our in-tree build backend did not do. This change switches away from our in-tree build backend to buildthings, giving us a consistent setup going forward and resolving several issues when building Djblets. When building Djblets, development and package dependencies will be installed in the isolated build environment for all build types, allowing static media to be built. All build types support `.local-packages`, since we need this in order to build and deploy in-development versions. Builds can be tested using: $ python -m build --sdist . $ python -m build --wheel . Doing these separately ensures that `.local-packages` will be picked up for each build type, rather than the default behavior of the wheel being built from the source distribution.	5089a2a310625f6714962508f9529f34c857e77d

Summary

Switch Djblets package building to use buildthings.

Buildthings is our new Python package build backend, which supports injecting local development source trees into the isolated build environment, interfacing with npm, and running extra build steps. It also notably allows for local paths for development dependencies, something our in-tree build backend did not do. This change switches away from our in-tree build backend to buildthings, giving us a consistent setup going forward and resolving several issues when building Djblets. When building Djblets, development and package dependencies will be installed in the isolated build environment for all build types, allowing static media to be built. All build types support `.local-packages`, since we need this in order to build and deploy in-development versions. Builds can be tested using: $ python -m build --sdist . $ python -m build --wheel . Doing these separately ensures that `.local-packages` will be picked up for each build type, rather than the default behavior of the wheel being built from the source distribution.

5089a2a310625f6714962508f9529f34c857e77d

Issues

Description	From	Last Updated
Should add , optional here now.	david	March 27, 2026, 10:32 a.m.
If we don't need developer deps, shouldn't include-dev-deps be False?	david	March 28, 2026, 2:09 a.m.
We should probably do build-i18n as well.	david	March 28, 2026, 2:13 a.m.
Should we also have prune .npm-workspaces?	david	March 28, 2026, 2:13 a.m.

flake8 passed.

JSHint passed.

djblets/dependencies.py (Diff revision 1)
The issue has been resolved. Show all issues
```
Should add , optional here now.
```

Change Summary:

Finalized the configuration based on the latest buildthings.

Description:

		Buildthings is our new Python package build backend, which supports
		injecting local development source trees into the isolated build
		environment, interfacing with npm, and running extra build steps.
		It also notably allows for local paths for development dependencies,
		something our in-tree build backend did not do.

		This change switches away from our in-tree build backend to
		buildthings, giving us a consistent setup going forward and resolving
		several issues when building Djblets.

		When building Djblets, development and package dependencies will be
		installed in the isolated build environment for all build types,
		allowing static media to be built.

~		Editable builds support `.local-packages`, but other build types do not
~		(since we don't want to run the risk of creating public builds that
	~	All build types support `.local-packages`, since we need this in order
	~	to build and deploy in-development versions.
-		can't be reproduced). For local testing, this can be enabled in the tree
-		using:

~
	~	Builds can be tested using:

~		`[tool.buildthings.isolation]`
~		local-packages-path = '.local-packages'
	~	`$ python -m build --sdist .`
	~	$ python -m build --wheel .


-
-
-		Then builds can be tested using:
-
-
-
-		`$ python -m build --sdist .`
-		$ python -m build --wheel .
-
-
-
-
		Doing these separately ensures that `.local-packages` will be picked up
		for each build type, rather than the default behavior of the wheel being
		built from the source distribution.

Commits:

	Summary	ID
	Switch Djblets package building to use buildthings. Buildthings is our new Python package build backend, which supports injecting local development source trees into the isolated build environment, interfacing with npm, and running extra build steps. It also notably allows for local paths for development dependencies, something our in-tree build backend did not do. This change switches away from our in-tree build backend to buildthings, giving us a consistent setup going forward and resolving several issues when building Djblets. When building Djblets, development and package dependencies will be installed in the isolated build environment for all build types, allowing static media to be built. Editable builds support `.local-packages`, but other build types do not (since we don't want to run the risk of creating public builds that can't be reproduced). For local testing, this can be enabled in the tree using: [tool.buildthings.isolation] local-packages-path = '.local-packages' Then builds can be tested using: $ python -m build --sdist . $ python -m build --wheel . Doing these separately ensures that `.local-packages` will be picked up for each build type, rather than the default behavior of the wheel being built from the source distribution.	683fa95b9740f44f979541ab476e88604b82dfe6
	Switch Djblets package building to use buildthings. Buildthings is our new Python package build backend, which supports injecting local development source trees into the isolated build environment, interfacing with npm, and running extra build steps. It also notably allows for local paths for development dependencies, something our in-tree build backend did not do. This change switches away from our in-tree build backend to buildthings, giving us a consistent setup going forward and resolving several issues when building Djblets. When building Djblets, development and package dependencies will be installed in the isolated build environment for all build types, allowing static media to be built. All build types support `.local-packages`, since we need this in order to build and deploy in-development versions. Builds can be tested using: $ python -m build --sdist . $ python -m build --wheel . Doing these separately ensures that `.local-packages` will be picked up for each build type, rather than the default behavior of the wheel being built from the source distribution.	a4ce229740a26bb2370c59218b6df5b934182988

Branch:

release-6.x

release-5.x

Diff:

Revision 2 (+148 -754)

Show changes

	.gitignore
	COPYING
	MANIFEST.in
	build-backend.py
	pyproject.toml
	djblets/dependencies.py

Checks run (2 succeeded)

flake8 passed.

JSHint passed.

pyproject.toml (Diff revisions 1 - 2)

The issue has been resolved. Show all issues

If we don't need developer deps, shouldn't include-dev-deps be False?

chipx86

March 28, 2026, 2:15 a.m.
```
Bad copy/paste from Review Board.
```

pyproject.toml (Diff revisions 1 - 2)
The issue has been resolved. Show all issues
```
We should probably do build-i18n as well.
```
MANIFEST.in (Diff revision 2)
The issue has been resolved. Show all issues
```
Should we also have prune .npm-workspaces?
```

Change Summary:


Fixed some comments in pyproject.toml.
Added the build-i18n steps.
Removed media and i18n building from the editable build.
Added npm management to sdist and wheel builds.
.npm-workspaces and node_modules are now explicitly pruned.

Commits:

	Summary	ID
	Switch Djblets package building to use buildthings. Buildthings is our new Python package build backend, which supports injecting local development source trees into the isolated build environment, interfacing with npm, and running extra build steps. It also notably allows for local paths for development dependencies, something our in-tree build backend did not do. This change switches away from our in-tree build backend to buildthings, giving us a consistent setup going forward and resolving several issues when building Djblets. When building Djblets, development and package dependencies will be installed in the isolated build environment for all build types, allowing static media to be built. All build types support `.local-packages`, since we need this in order to build and deploy in-development versions. Builds can be tested using: $ python -m build --sdist . $ python -m build --wheel . Doing these separately ensures that `.local-packages` will be picked up for each build type, rather than the default behavior of the wheel being built from the source distribution.	a4ce229740a26bb2370c59218b6df5b934182988
	Switch Djblets package building to use buildthings. Buildthings is our new Python package build backend, which supports injecting local development source trees into the isolated build environment, interfacing with npm, and running extra build steps. It also notably allows for local paths for development dependencies, something our in-tree build backend did not do. This change switches away from our in-tree build backend to buildthings, giving us a consistent setup going forward and resolving several issues when building Djblets. When building Djblets, development and package dependencies will be installed in the isolated build environment for all build types, allowing static media to be built. All build types support `.local-packages`, since we need this in order to build and deploy in-development versions. Builds can be tested using: $ python -m build --sdist . $ python -m build --wheel . Doing these separately ensures that `.local-packages` will be picked up for each build type, rather than the default behavior of the wheel being built from the source distribution.	5089a2a310625f6714962508f9529f34c857e77d

Diff:

Revision 3 (+182 -754)

Show changes

	.gitignore
	COPYING
	MANIFEST.in
	build-backend.py
	pyproject.toml
	djblets/dependencies.py

Checks run (2 succeeded)

flake8 passed.

JSHint passed.

Ship it!

```
Ship It!
```

Status:: Completed
Change Summary:: Pushed to release-5.x (4e2edbe)