Skip to content

Explain build frontend vs. build backend #11094

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 30, 2025
Merged

Explain build frontend vs. build backend #11094

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6a059e0
Explain build frontend vs. build backend
konstin Jan 30, 2025
420ec71
Update docs/concepts/projects/build.md
konstin Jan 30, 2025
15e1005
Edits
zanieb Jan 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/concepts/projects/build.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,14 @@ distributions (wheels). The former is typically a `.tar.gz` or `.zip` file conta
source code along with some additional metadata, while the latter is a `.whl` file containing
pre-built artifacts that can be installed directly.

!!! important

When using `uv build`, uv acts as a [build frontend](https://peps.python.org/pep-0517/#terminology-and-goals)
and only determines the Python version to use and invokes the build backend. The details of
the builds, such as the included files and the distribution filenames, are determined by the build
backend, as defined in [`[build-system]`](./config.md#build-systems). Information about build
configuration can be found in the respective tool's documentation.

## Using `uv build`

`uv build` can be used to build both source distributions and binary distributions for your project.
Expand Down
Loading