featured · github
Black: Stop Arguing About Python Formatting and Start Shipping
The opinionated code formatter that eliminates style debates in pull requests. One command, zero decisions, hours of review time saved.
psf/black ↗Black is a code formatter for Python that makes all your code look the same without you having to think about it. Here's why that matters: instead of spending review time debating whether a line should be 79 or 88 characters, you run black . and move on. It enforces one style everywhere—no configuration, no choices. For teams, this kills bikeshedding in PRs. For solopreneurs, it's one fewer thing to manually fix before shipping. It integrates into CI/CD pipelines and most editors, so formatting happens automatically on save. If you're writing Python at any scale, Black is the default move. It's not new, but it's become table-stakes tooling because it actually works.
Share kit
Black: The Python formatter that ends style debates
Stop spending review cycles on spacing and line length. Black auto-formats Python code to a single standard—zero configuration, integrates into CI/CD and editors. If your team writes Python, this saves real hours per week.
Black isn't revolutionary. It's just the Python formatter that actually stuck because it kills the style debate. Run it, ship code faster, move on. Now table-stakes for anyone writing Python at scale.
For Python teams: Black eliminates style review friction by enforcing one opinionated format. Auto-format on save, integrate into CI/CD, reclaim hours spent debating line length. It's become the default for good reason.
Just realized: I've stopped arguing about Python formatting. Black did that. We adopted it across our codebase two years ago. What I didn't expect wasn't the speed—it's that code review friction just evaporated. No more "use two spaces" threads. No more tabs vs. spaces. No more time spent on style nits that should've been automated away. Black is uncompromising by design. You don't configure it. It formats your Python, period. Integrates into pre-commit hooks, CI/CD, your editor. One command and you're done. For teams shipping Python, this is table-stakes now. It's been downloaded millions of times, backed by the Python Software Foundation, and it solves a real problem: style debate is expensive and dumb to have manually. If you're still hand-formatting or debating style in PRs, you're leaving hours on the table every sprint. https://github.com/psf/black
Spent 3 hours last week watching a team debate Python formatting in a PR. Black solves this in 30 seconds. No config, no negotiation. Just opinionated, consistent code. One command. Done. Review your logic instead of your commas. https://github.com/psf/black