POpolygot·Dec 5, 2017Submission
Automatically format Python code so that it meets PEP8 standards
2 points · Open discussionhhatto
autopep8
Python2012–2017
hhatto / autopep8
autopep8
A tool that automatically formats Python code to conform to the PEP 8 style guide.
5Distinct people
6Mentions
0Explicit recommenders
4.7KGitHub stars
What to know before exploring
What it is
A tool that automatically formats Python code to conform to the PEP 8 style guide.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year6 dated mentions
Observed mentions: 2012-09-08 03:42:55 UTC to 2017-12-05 05:08:44 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
6 sourcesI'm not super familiar with python, but I've tried using a pep8 auto formatter and it seemed to reformat it to comply to standards https://github.com/hhatto/autopep8
Perhaps that could be useful when having to write pep8 compliant code but don't want to manually format everything.
In Ask HN: In your company, how important is code quality vs. getting things doneA tool that formats Python code to conform to the PEP 8 style guide
4 points · Open discussionYou can do that with Python code, too.
https://github.com/hhatto/autopep8
In Plan 9 Coding Conventions for CThis isn't static analysis.
Compare the output of a "real" static analysis tool that finds logic bugs[0]
https://www.dropbox.com/s/md35ca9mjrny4o1/Screen%20Shot%2020...
With their whitespace recommendations
https://codeq.io/github/tianyang-li/rna-seq-len-est-0/master...
Which seem to mostly be a wrapper around autopep8: https://github.com/hhatto/autopep8.
Even Pylint / Pyflakes would be more "static analyzer" than this tool, although it's a stretch.
[0] In this case it trips an assert, so the bug can't "really" happen. Still, it's pretty impressive stuff.
In Codeq. Code quality as a serviceWith this tool,automatically generate pep8 checked python code
1 points · Open discussion