[GSoC-general] Sharing a tool for the Python community which helps in code style review

[Himanshu Mishra]

Dear Mentors,

Two years ago, I was a student of Google Summer of Code under Python
Software Foundation. Since then, almost all the times, I have seen 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.

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 these things in mind, I have created something called PEP8 Speaks
<https://github.com/OrkoHunter/pep8speaks>[1] and I would love to hear the
feedback from the Python community. It works only for public repositories
as of now.

I would also like to know why or why not would you be using this in future.

[1] https://github.com/OrkoHunter/pep8speaks

Thank you.
-- 
Himanshu Mishra
Third Year Undergraduate
Mathematics and Computing
IIT Kharagpur
http://orkohunter.net
-- 
Himanshu Mishra
Third Year Undergraduate
Mathematics and Computing
IIT Kharagpur
http://orkohunter.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/gsoc-general/attachments/20170108/2589770c/attachment.html>