python-build を Homebrew, pacman, apt, dnf, zypper でインストール

プロジェクトリンク

• ホームページ
• パッケージマネージャページ

コマンドとエイリアス

• pyproject-build

プロジェクトの歴史

PEP 517 standardized a build-system-independent interface between frontends and backends, while pyproject.toml records the selected backend and its requirements. build was created to provide a focused, standards-following frontend for this model.

The initial public release appeared in 2020. The project moved under the Python Packaging Authority later that year, adopted isolated builds by default, and eventually reached a stable 1.0 release.

採用の歴史

build became common packaging infrastructure by giving maintainers a backend-neutral command for producing source distributions and wheels. It is used in local release preparation, continuous integration, packaging tutorials, and downstream checks of PEP 517 source trees.

The project is distributed under differing ecosystem names: PyPI calls it build, Homebrew uses python-build, and several Linux distributions use python3-build or python-build.

使われ方

Run python -m build in a Python project to create both an sdist and a wheel, or select an individual artifact type with command-line options.

The project-level pyproject.toml declares the backend and build requirements. build is a frontend and does not replace the selected backend.

パッケージ好きにとっての重要性

build embodies the modern separation between a build frontend and backends such as setuptools, Flit, or Hatchling. Package maintainers value it as a small reference workflow that exercises the standardized hooks instead of invoking setup.py directly.

Its isolated-build behavior helps reveal incomplete build requirements and supports reproducible packaging workflows without tying a project to one backend.

タイムライン

• 2015: PEP 517 was created to standardize build frontend and backend interaction.
• 2020: build's initial public release appeared.
• 2020: The project moved under PyPA and renamed its executable to pyproject-build.
• 2021: The CLI began building wheels from the generated source distribution by default.
• 2023: The project replaced the renamed pep517 library with pyproject-hooks.
• 2023: build reached its 1.0 release.

Related projects

• PEP 517 defines the frontend/backend interface implemented by build.
• pyproject.toml supplies the build-system requirements and backend selection read by build.
• Twine commonly follows build in release workflows by uploading the resulting distributions.

ソース

• https://build.pypa.io/en/latest/
• https://build.pypa.io/en/latest/explanation/how-it-works.html
• https://github.com/pypa/build/blob/main/CHANGELOG.rst
• https://packaging.python.org/en/latest/flow/
• https://peps.python.org/pep-0517/