# Install autopep8 with Homebrew, apt, pacman Automatically formats Python code to conform to the PEP 8 style guide. Version 2.3.2 via Homebrew; verified from local package data. ## Install ```sh sudo av install brew:autopep8 ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install autopep8 ``` Evidence: local Homebrew formula metadata ### Linux - Debian apt (92%): ```sh sudo apt install python3-autopep8 ``` Evidence: Debian stable package indexes: python3-autopep8 from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz - pacman (92%): ```sh sudo pacman -S autopep8 ``` Evidence: Arch Linux sync databases: autopep8 from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ## Package facts - **Package key:** brew:autopep8 - **Package manager:** Homebrew - **Package manager page:** - **Version:** 2.3.2 - **Source summary:** Automatically formats Python code to conform to the PEP 8 style guide - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** MIT - **Source archive:** - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - autopep8 (cli) - autopep8 (alias) ## Dependencies - python@3.14 ## Install behavior - Post-install hook: not defined - Bottle: available on all ## Freshness - Page generated: 2026-07-08 - Package-manager version: 2.3.2 - Local data: ok - Upstream repository: https://github.com/hhatto/autopep8 - info: No package-manager update timestamp was available. - info: No cached GitHub release or tag data was available. ## Project history and usage 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. ### Project history 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. ### Adoption history 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. ### How it is used 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. ### Why package nerds care 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. ### Timeline - 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 ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - 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 ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** autopep8 - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - 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 ## Related links - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [python@3.14](https://www.automicvault.com/pkg/brew/python-3-14/) - Runtime dependency declared by Homebrew. - [black](https://www.automicvault.com/pkg/brew/black/) - Shares av.db curated category or tags: cli, developer-tools, formatter, python. - [darker](https://www.automicvault.com/pkg/brew/darker/) - Shares av.db curated category or tags: cli, developer-tools, formatter, python. - [djhtml](https://www.automicvault.com/pkg/brew/djhtml/) - Shares av.db curated category or tags: cli, developer-tools, formatter, python. - [fprettify](https://www.automicvault.com/pkg/brew/fprettify/) - Shares av.db curated category or tags: cli, developer-tools, formatter, python. - [gersemi](https://www.automicvault.com/pkg/brew/gersemi/) - Shares av.db curated category or tags: cli, developer-tools, formatter, python. - [isort](https://www.automicvault.com/pkg/brew/isort/) - Shares av.db curated category or tags: cli, developer-tools, formatter, python. - [mdformat](https://www.automicvault.com/pkg/brew/mdformat/) - Shares av.db curated category or tags: cli, developer-tools, formatter, python. - [snakefmt](https://www.automicvault.com/pkg/brew/snakefmt/) - Shares av.db curated category or tags: cli, developer-tools, formatter, python. - [yapf](https://www.automicvault.com/pkg/brew/yapf/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, code, developer, developer-tools, formatter. ## Combined YAML source View the package source record on GitHub. [combined/autopep8.yml](https://github.com/automic-vault/db/blob/main/combined/autopep8.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph