Builds are configured using the
tool.hatch.build table. Every target is defined by a section within
tool.hatch.build.targets, for example:
[tool.hatch.build.targets.sdist] exclude = [ "/.github", "/docs", ] [tool.hatch.build.targets.wheel] packages = ["src/foo"]
[build.targets.sdist] exclude = [ "/.github", "/docs", ] [build.targets.wheel] packages = ["src/foo"]
build command without any arguments will build the sdist and wheel targets:
$ hatch build [sdist] dist/hatch_demo-1rc0.tar.gz [wheel] dist/hatch_demo-1rc0-py3-none-any.whl
To only build specific targets, use the
$ hatch build -t wheel [wheel] dist/hatch_demo-1rc0-py3-none-any.whl
If the target supports multiple versions, you can specify the exact versions to build by appending a colon followed by the desired versions separated by commas:
$ hatch -v build -t wheel:standard [wheel] Building `wheel` version `standard` dist/hatch_demo-1rc0-py3-none-any.whl
Hatch complies with modern Python packaging specs and therefore your projects can be used by other tools with Hatch serving as just the build backend.
So you could use tox as an alternative to Hatch's environment management, or cibuildwheel to distribute packages for every platform, and they both will transparently use Hatch without any extra modification.