Installer tox avec Homebrew, apt, dnf, pacman, zypper

Liens du projet

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

Commandes et alias

• tox

Historique du projet

The tox documentation describes modern tox as the second implementation of the project. The first implementation ran from version 0.5 through the 3.x series; version 4.0.0a1 began a complete rewrite, and the public 4.0.0 release followed in December 2022.

The project presents itself as part of a larger Python packaging and testing workflow alongside pytest and devpi. Its README emphasizes standardizing the packaging, testing, and release process, not merely launching test commands.

Historique d'adoption

tox became common in Python package maintenance because it solved a recurring packaging problem: checking that a package builds and installs correctly under multiple Python versions, interpreters, dependency sets, and CI environments from one local configuration.

The Homebrew source facts show tox packaged not only for Homebrew but also for Debian, Ubuntu, Fedora/dnf, Arch/pacman, and openSUSE/zypper. That cross-distribution packaging mirrors its long-standing role as a default developer tool for Python maintainers.

Modes d'utilisation

A typical tox project declares environments and commands in tox configuration, then runs `tox` locally or in CI. tox creates isolated virtual environments, installs dependencies and the package under test, and invokes the configured commands for each environment.

The current docs also document plugin extension points and companion plugins such as tox-uv, where tox remains the orchestration layer while another backend supplies environment creation or package installation behavior.

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

For package nerds, tox is one of the canonical Python packaging test tools: it turns the install-test cycle into a reproducible command, catches packaging mistakes before release, and lets maintainers run the same environment matrix locally that CI will run remotely.

Its importance is not just testing but package metadata hygiene. By forcing the package to install into clean environments before tests run, tox catches missing dependencies, broken build configuration, and environment assumptions that ordinary in-tree test runs can hide.

Chronologie

• 2010: PyPI records tox 0.5, the start of the first numbered implementation line noted by the tox changelog.
• 2022: tox 4.0.0 released after the complete rewrite documented in the tox changelog.
• 2026: tox 4.x remains active, with the latest docs listing regular 4.5x releases and plugin/onboarding documentation.

Related projects

• The tox README explicitly places tox alongside pytest and devpi in Python packaging and release workflows.
• tox-uv, tox-conda, and tox-docker are examples of ecosystem plugins that extend tox's environment runner or test orchestration model.

Sources

• https://github.com/tox-dev/tox#readme
• https://pypi.org/pypi/tox/json
• https://tox.wiki/en/latest/changelog.html
• https://tox.wiki/en/latest/config.html
• source_facts.package-manager