# flit を Homebrew, apt, dnf でインストール flit のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。 ## インストール ```sh sudo av install brew:flit ``` 追加のインストールコマンド: ### macOS - Homebrew (100%): ```sh brew install flit ``` 証拠: local Homebrew formula metadata ### Linux - Debian apt (92%): ```sh sudo apt install flit ``` 証拠: Debian stable package indexes: flit from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz - dnf (92%): ```sh sudo dnf install flit ``` 証拠: Fedora Rawhide package metadata: flit from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst ## パッケージ情報 - **パッケージキー:** brew:flit - **パッケージマネージャ:** Homebrew - **バージョン:** 3.12.0 - **ソース概要:** Simplified packaging of Python modules - **ホームページ:** - **リポジトリ:** - **最終更新:** 2026-05-21T11:31:14Z - **生成日時:** 2026-08-03T19:37:03+00:00 ## 実行可能ファイル - flit (エイリアス) ## インストール挙動 - Bottle: 利用不可 ## バージョンと鮮度 - ページ生成日: 2026-08-03 - マネージャ版: 3.12.0 ## プロジェクトの歴史と使われ方 Flit is a Python packaging tool for publishing modules and packages to PyPI with a small amount of project metadata. It became notable in Python packaging culture as an early, opinionated tool built around pyproject.toml and the PEP 517 build-backend model rather than the older setup.py workflow. ### プロジェクトの歴史 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. ### 採用の歴史 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. ### 使われ方 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. ### パッケージ好きにとっての重要性 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. ### タイムライン - 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. ### ソース - - - - ## セキュリティノート flit に一致するローカルシークレット処理マニフェストは見つかりませんでした。将来の対応で安定したパッケージ URL を使えるよう、Nucleus パッケージメタデータはここに公開されています。 ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: pyproject.toml ## Credential files - Unix: ~/.pypirc ## 他のパッケージマネージャ記録 - Debian apt - flit - 3.12.0-1: normalized package name match | Debian stable package indexes: flit from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | simple way to put Python packages and modules on PyPI (PEP 517) | https://flit.readthedocs.io/en/latest/ - Ubuntu apt - flit - 3.9.0-2: normalized package name match | Ubuntu 24.04 LTS package indexes: flit from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | simple way to put Python packages and modules on PyPI (PEP 517) | https://flit.readthedocs.io/en/latest/ - dnf - flit - 3.12.0-9.fc45: normalized package name match | Fedora Rawhide package metadata: flit from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | Simplified packaging of Python modules | https://flit.pypa.io/ ## Combined YAML source View the package source record on GitHub. [combined/flit.yml](https://github.com/mxcl/pkgdb/blob/main/combined/flit.yml) ## ソース - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph