Installer flit avec Homebrew, apt, dnf

Liens du projet

• Page d'accueil
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• flit

Historique du projet

The project appeared on PyPI in 2015 and describes itself as a simple way to put Python packages and modules on PyPI while avoiding common packaging mistakes. Its workflow centers on running flit init to create pyproject.toml, then using flit publish or flit install for distribution and local development.

Flit's documentation records the evolution from the very old flit.ini format, to the older [tool.flit.metadata] table, and then to the standard [project] table. The same documentation identifies flit_core as the build backend used by pip and other build frontends.

Historique d'adoption

Flit was adopted by Python projects that wanted a low-boilerplate packaging path for single import packages and modules. Its role grew with standard pyproject.toml metadata, because it offered a compact implementation of the modern build-backend approach.

The package is distributed through PyPI and is also curated by operating-system package managers, including Homebrew and several Linux distributions in the supplied package facts.

Modes d'utilisation

Typical use starts with python3 -m pip install flit, then flit init in a project directory to create pyproject.toml. Publishing is done with flit publish, and development installs use flit install with optional symlink and interpreter flags.

Flit is intentionally narrow: it packages one importable module or package at a time, reads common metadata from pyproject.toml and the module, and delegates standard wheel installation behavior to pip.

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

Flit is significant to package maintainers because it made pyproject.toml-first packaging feel practical before that workflow became routine. It is also a useful reference point for the division between a frontend CLI, flit, and a backend package, flit_core.

For package-index and distribution maintainers, Flit is a clean example of PEP 517-era packaging: projects can declare flit_core.buildapi in [build-system], allowing build tools to construct wheels without executing setup.py.

Chronologie

• 2015: Flit 0.1 is uploaded to PyPI.
• 2016: Early 0.x releases continue the simple PyPI publishing workflow.
• 2020: Flit 3.x era documentation supports the standard [project] metadata table.
• 2026: PyPI metadata reports Flit 3.12.0 as the current release during this enrichment run.

Related projects

• flit_core is the build backend used in pyproject.toml for Flit-built packages.
• pip consumes Flit-built wheels and can invoke Flit in an isolated build environment for source distributions.
• setuptools and other Python packaging tools are the broader ecosystem that Flit is commonly compared against.

Sources

• https://flit.pypa.io/en/stable/
• https://flit.pypa.io/en/stable/pyproject_toml.html
• https://github.com/pypa/flit
• https://pypi.org/pypi/flit/json