HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pep8speaks-org
pep8speaks
Python2016–2017
pep8speaks-org / pep8speaks

pep8speaks

A GitHub :octocat: app to automatically review Python code style over Pull Requests

3Distinct people
7Mentions
0Explicit recommenders
620GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A GitHub :octocat: app to automatically review Python code style over Pull Requests

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 week7 dated mentions

Observed mentions: 2016-12-27 22:34:22 UTC to 2017-07-03 05:23:43 UTC. Weeks start Monday, UTC.

01232016-12-26 00:00:00 UTC to 2017-01-02 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 commentsDec 262017-01-02 00:00:00 UTC to 2017-01-09 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2017-01-09 00:00:00 UTC to 2017-01-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-16 00:00:00 UTC to 2017-01-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-23 00:00:00 UTC to 2017-01-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-30 00:00:00 UTC to 2017-02-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-06 00:00:00 UTC to 2017-02-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-13 00:00:00 UTC to 2017-02-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-20 00:00:00 UTC to 2017-02-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-27 00:00:00 UTC to 2017-03-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-06 00:00:00 UTC to 2017-03-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-13 00:00:00 UTC to 2017-03-20 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2017-03-20 00:00:00 UTC to 2017-03-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-27 00:00:00 UTC to 2017-04-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 272017-04-03 00:00:00 UTC to 2017-04-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-04-10 00:00:00 UTC to 2017-04-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-04-17 00:00:00 UTC to 2017-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-04-24 00:00:00 UTC to 2017-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-05-01 00:00:00 UTC to 2017-05-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-05-08 00:00:00 UTC to 2017-05-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-05-15 00:00:00 UTC to 2017-05-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-05-22 00:00:00 UTC to 2017-05-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-05-29 00:00:00 UTC to 2017-06-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-06-05 00:00:00 UTC to 2017-06-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-06-12 00:00:00 UTC to 2017-06-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-06-19 00:00:00 UTC to 2017-06-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-06-26 00:00:00 UTC to 2017-07-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-03 00:00:00 UTC to 2017-07-10 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJul 3

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 262016-12-26 00:00:00 UTC2017-01-02 00:00:00 UTC321
Jan 22017-01-02 00:00:00 UTC2017-01-09 00:00:00 UTC110
Jan 92017-01-09 00:00:00 UTC2017-01-16 00:00:00 UTC000
Jan 162017-01-16 00:00:00 UTC2017-01-23 00:00:00 UTC000
Jan 232017-01-23 00:00:00 UTC2017-01-30 00:00:00 UTC000
Jan 302017-01-30 00:00:00 UTC2017-02-06 00:00:00 UTC000
Feb 62017-02-06 00:00:00 UTC2017-02-13 00:00:00 UTC000
Feb 132017-02-13 00:00:00 UTC2017-02-20 00:00:00 UTC000
Feb 202017-02-20 00:00:00 UTC2017-02-27 00:00:00 UTC000
Feb 272017-02-27 00:00:00 UTC2017-03-06 00:00:00 UTC000
Mar 62017-03-06 00:00:00 UTC2017-03-13 00:00:00 UTC000
Mar 132017-03-13 00:00:00 UTC2017-03-20 00:00:00 UTC220
Mar 202017-03-20 00:00:00 UTC2017-03-27 00:00:00 UTC000
Mar 272017-03-27 00:00:00 UTC2017-04-03 00:00:00 UTC000
Apr 32017-04-03 00:00:00 UTC2017-04-10 00:00:00 UTC000
Apr 102017-04-10 00:00:00 UTC2017-04-17 00:00:00 UTC000
Apr 172017-04-17 00:00:00 UTC2017-04-24 00:00:00 UTC000
Apr 242017-04-24 00:00:00 UTC2017-05-01 00:00:00 UTC000
May 12017-05-01 00:00:00 UTC2017-05-08 00:00:00 UTC000
May 82017-05-08 00:00:00 UTC2017-05-15 00:00:00 UTC000
May 152017-05-15 00:00:00 UTC2017-05-22 00:00:00 UTC000
May 222017-05-22 00:00:00 UTC2017-05-29 00:00:00 UTC000
May 292017-05-29 00:00:00 UTC2017-06-05 00:00:00 UTC000
Jun 52017-06-05 00:00:00 UTC2017-06-12 00:00:00 UTC000
Jun 122017-06-12 00:00:00 UTC2017-06-19 00:00:00 UTC000
Jun 192017-06-19 00:00:00 UTC2017-06-26 00:00:00 UTC000
Jun 262017-06-26 00:00:00 UTC2017-07-03 00:00:00 UTC000
Jul 32017-07-03 00:00:00 UTC2017-07-10 00:00:00 UTC110

What Hacker News says

7 sources

Show HN: A GitHub integration for Python code style

Hey everyone, I have been in the Python developers community for around 2.5 years now. And almost all the times, I have seen the mentors requesting the contributors to do a "minor but very important" thing to do, fix their code style. Sometimes the contributors are very beginner and the reviewers have to manually comment every line with PEP8 issues. We understand that the Pull Request author must fix the style on their side before submitting the PR, but we know that people don't do that all the times. Now some libraries have the option of adding linter to the Travis CI itself. But seeing the entire build fail only because of a missing whitespace does not seem to be a clever choice. And if there is a green tick outside, the PR author is never going to open it up and see the lint results! Keeping all the situations in mind, I have created s
Read the rest
omething called pep8speaks[1] and I would love to hear your feedback. I would also like to know why or why not would you be using this in future. Thank you. [1]. https://github.com/OrkoHunter/pep8speaks
3 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.