Skip to content
Back to top
View this page

# Installation

## Installing via pip

`build` can be installed via pip or an equivalent:

    $ pip install build

You can also check out the latest git tag, download a tarball from GitHub, or manually fetch the artifacts from the project page on PyPI. Attestations are available after 1.2.1 and can be verified with the `gh` CLI tool:

    $ python -m pip --no-cache-dir download --no-deps build
    $ gh attestation verify build*.whl --repo pypa/build

Build plans to support PEP 740 if accepted.

Tip

If you prefer, or are already using virtualenv in your workflow, you can install `build` with the optional `virtualenv` dependency:

    $ pip install 'build[virtualenv]'

this way, `build` will use virtualenv for isolation, instead of venv. This can be particularly useful, for example, when using automation tools that rely on virtualenv, such as tox, or when your operating system’s Python package does not include venv in the standard installation (such as some versions of Ubuntu).

There is also a `uv` extra, which can be used for `--installer=uv` if you don’t have another install of `uv` available.

## Installing via conda

On conda-forge, this package is called python-build, therefore it can be installed via conda or an equivalent:

    $ conda install conda-forge::python-build

## Bootstrapping

This package can build itself only with the `tomli` (can be omitted in Python 3.11+) and `pyproject-hooks` dependencies. The `--skip-dependency-check` flag should be used in this case.

## Compatibility

`build` is verified to be compatible with the following Python versions:

- 3.9

- 3.10

- 3.11

- 3.12

- 3.13

- PyPy3