# Installer autopep8 avec Homebrew, pacman, apt Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de autopep8 pour les workflows d'agents IA. ## installation ```sh sudo av install brew:autopep8 ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install autopep8 ``` Preuve: local Homebrew formula metadata ### Linux - pacman (92%): ```sh sudo pacman -S autopep8 ``` Preuve: Arch Linux sync databases: autopep8 from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz - Debian apt (92%): ```sh sudo apt install python3-autopep8 ``` Preuve: Debian stable package indexes: python3-autopep8 from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz ## Faits du paquet - **Clé du paquet:** brew:autopep8 - **Gestionnaire de paquets:** Homebrew - **Version:** 2.3.2 - **Résumé source:** Automatically formats Python code to conform to the PEP 8 style guide - **Page d'accueil:** - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - autopep8 (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 2.3.2 ## Historique du projet et usages autopep8 is a Python formatter that uses pycodestyle diagnostics to rewrite code toward PEP 8. It predates the Black era of Python formatting and represents the earlier style of configurable, error-code-driven automatic cleanup. ### Historique du projet The official GitHub repository was created in December 2010. The README describes autopep8 as a tool that automatically formats Python code to conform to PEP 8, using pycodestyle to determine which parts need formatting. The project grew around pycodestyle error codes: the README lists many E and W codes autopep8 can fix, plus conservative defaults and more aggressive modes for changes that may affect semantics. ### Historique d'adoption autopep8 spread through Python packaging and editor integrations as a command-line formatter. The batch input lists Homebrew plus Debian/Ubuntu and Arch packages, while the official README points users to pip, PyPI, GitHub, and pre-commit hook usage. Its GitHub metadata shows thousands of stars and hundreds of forks, consistent with long-running use in Python developer workflows even as opinionated formatters became more prominent later. ### Modes d'utilisation Common usage is autopep8 --in-place with one or more --aggressive flags, or --diff for review. The README also documents module use through fix_code(), recursive operation, parallel jobs, line ranges, pre-commit integration, and pyproject.toml support. Configuration can come from a global pycodestyle file, project files such as setup.cfg, tox.ini, .pep8, and .flake8, or pyproject.toml under [tool.autopep8], which takes precedence over other configuration files. ### Pourquoi les passionnés de paquets s'y intéressent autopep8 is useful to package nerds because it bridges Python packaging, linter configuration, editor formatting, and pre-commit automation without imposing a single style regime. Its behavior is legible in terms of pycodestyle codes, which makes distro and CI behavior easier to explain than opaque formatter output. ### Chronologie - 2010: hhatto/autopep8 GitHub repository created. - 2010s: autopep8 becomes a common PEP 8 cleanup command distributed through PyPI and OS package managers. - 2020s: autopep8 continues supporting pyproject.toml, pre-commit, modern Python versions, and pycodestyle-based fixes. ### Related projects - pycodestyle supplies the style diagnostics autopep8 uses. - flake8 and pep8-style configuration files influence autopep8 configuration discovery. - Black, yapf, docformatter, and eradicate are adjacent Python formatting or cleanup tools. ### Sources - - - source_facts.package-manager ## Notes de sécurité narrow executable package without higher-risk signals. - **Risque Geiger:** vert / faible - narrow executable package without higher-risk signals ## 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: ~/.config/pycodestyle, setup.cfg, tox.ini, .pep8, .flake8, pyproject.toml - Windows: ~\.pycodestyle, setup.cfg, tox.ini, .pep8, .flake8, pyproject.toml ## Autres enregistrements de gestionnaires de paquets - Debian apt - python3-autopep8 - 2.3.2-1: normalized package name match | Debian stable package indexes: python3-autopep8 from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | tool that automatically formats Python code to conform to PEP 8 | https://github.com/hhatto/autopep8 - Ubuntu apt - python3-autopep8 - 2.0.4-2: normalized package name match | Ubuntu 24.04 LTS package indexes: python3-autopep8 from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | tool that automatically formats Python code to conform to PEP 8 | https://github.com/hhatto/autopep8 - pacman - autopep8 - 1:2.3.2-2: normalized package name match | Arch Linux sync databases: autopep8 from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A tool that automatically formats Python code to conform to the PEP 8 style guide | https://github.com/hhatto/autopep8 ## Combined YAML source View the package source record on GitHub. [combined/autopep8.yml](https://github.com/mxcl/pkgdb/blob/main/combined/autopep8.yml) ## Sources - 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