Installer pip-tools avec Homebrew

Liens du projet

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

Commandes et alias

• pip-compile
• pip-sync

Historique du projet

pip-tools evolved as a pair of focused commands around pip: pip-compile resolves abstract dependency declarations into pinned requirements, while pip-sync makes an environment match compiled files. The project is now maintained in the Jazzband organization.

Historique d'adoption

pip-tools became a widely packaged companion to pip and is listed by the Python Packaging Authority among key packaging projects. Stewardship under Jazzband gives it a community-maintained project home, while integrations such as pre-commit support place dependency compilation in routine development workflows.

Modes d'utilisation

pip-compile reads dependencies from pyproject.toml, setup.cfg, setup.py, or requirements.in and writes pinned requirements files. pip-sync then installs, upgrades, or removes packages so an environment matches those compiled files. Compilation should be performed for each target Python environment when dependency markers can produce platform-specific results.

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

pip-tools popularized a lightweight input-versus-lock workflow before Python standardized a universal application lock file: developers declare broad requirements, compile exact transitive pins, and synchronize environments to those pins. It remains attractive because its output is ordinary pip-compatible requirements files.

Chronologie

• 2010s: pip-tools established the pip-compile and pip-sync workflow.
• Later development: Project stewardship moved under Jazzband and support expanded to modern pyproject.toml metadata and pip's backtracking resolver.

Related projects

• pip
• PyPI
• Jazzband
• pipenv
• Poetry
• uv

Sources

• https://github.com/jazzband/pip-tools
• https://packaging.python.org/en/latest/key_projects/
• https://pip-tools.readthedocs.io/en/stable/