Installer hatch avec Homebrew, apk, dnf, MacPorts, Nix, scoop, winget

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• hatch

Historique du projet

The Hatch history page records version 1.0.0 on 2022-04-28 as the first stable release of Hatch v1 and a complete rewrite. The adjacent Hatchling history records 0.24.0 on the same date as the initial public release of the Hatchling build system, establishing the split between the user-facing Hatch CLI and the build backend.

The 1.1.0 history entry says project metadata was updated to reflect adoption by PyPA and production stability. That matters historically because PyPA ownership placed Hatch among the packaging tools documented and maintained in the Python packaging ecosystem rather than as only an individual project.

Later history entries show Hatch broadening from packaging and environments into batteries-included project operations: publishing confirmation and index plugins, virtual-environment storage and plugin APIs, automatic Python distribution downloads, test commands, static analysis defaults, standalone binaries through PyApp, UV support, dependency groups, workspaces, and PEP 751 lockfile commands.

Historique d'adoption

Hatch adoption came from Python projects that wanted a single pyproject.toml-native workflow for building, testing, versioning, environment scripts, and publishing. Its README presents standardized builds, reproducible builds by default, environment management, Python management, test execution, static analysis, script running, publishing, version management, and project generation as first-class features.

The build documentation emphasizes that Hatch complies with modern Python packaging specifications and that other tools can consume projects using Hatch as a build backend. This is central to adoption: projects can use Hatchling while still interoperating with pip, tox, cibuildwheel, PyPI, and other packaging tools.

Package-manager adoption reflects that dual role. Homebrew and other OS package managers distribute the hatch CLI, while Python packaging itself consumes Hatchling through build-system requirements in pyproject.toml.

Modes d'utilisation

Typical CLI workflows include hatch new, hatch build, hatch publish, hatch version, hatch run, hatch env commands, hatch test, and Hatch-managed Python or environment operations. Configuration lives in user config files plus pyproject.toml or hatch.toml project tables.

As a build backend, Hatchling is declared in pyproject.toml with build-system.requires and build-backend. As a workflow manager, Hatch creates and runs named environments, executes scripts, builds distributions, and coordinates publishing without forcing all projects to abandon other tools in the packaging ecosystem.

Pourquoi les passionnés de paquets s'y intéressent

Hatch is significant because it bundles several trends in Python packaging: pyproject.toml configuration, backend/front-end separation, reproducible builds, environment automation, plugin hooks, and standards-based metadata. It is not just a build backend and not just a virtualenv wrapper.

For package nerds, Hatchling's small build-backend role is as important as the hatch CLI. A project can depend on Hatchling for wheel and sdist creation while developers use Hatch for environments, scripts, tests, versions, and publishing.

The changelog also tracks the moving Python packaging target: Python version support drops, metadata version updates, SBOM support, dependency groups, UV integration, lockfiles, PyPI telemetry user agents, and workspace concepts all appear as the ecosystem evolves.

Chronologie

• 2022-04-28: Hatch 1.0.0 shipped as the first stable v1 release and complete rewrite; Hatchling 0.24.0 shipped as the initial public build-system release.
• 2022-05-12: Hatch 1.1.0 updated project metadata to reflect PyPA adoption and production stability.
• 2023: Hatch added and refined publishing, virtual environment behavior, build backend flexibility, automatic Python downloads, and plugin interfaces.
• 2024: Hatch added a test command, UV support for virtual environments, official GitHub Action support, and Python distribution source controls.
• 2025: Hatch 1.16.0 added workspace support inspired by Cargo Workspaces and dependency group support.
• 2026: Hatch 1.17.0 added check commands, PEP 751 lockfile generation, dependency lock/sync commands, and pluggable dependency lockers.

Related projects

• Hatchling is Hatch's build backend and is declared by projects through pyproject.toml.
• PyPA is the Python Packaging Authority organization under which Hatch is maintained.
• PyPI, pip, tox, cibuildwheel, virtualenv, UV, Ruff, PyApp, and Python packaging standards are recurring integration points in Hatch documentation and history.

Sources

• https://formulae.brew.sh/formula/hatch
• https://github.com/pypa/hatch
• https://hatch.pypa.io/
• https://hatch.pypa.io/1.12/history/hatchling/
• https://hatch.pypa.io/1.16/build/
• https://hatch.pypa.io/1.16/why/
• https://hatch.pypa.io/dev/history/hatch/