One good parts of Go is gofmt, the standard code formatter.
It makes learning Go more easy and fun.
New Gophers can learn Go without learning coding style which gofmt handles.

Python doesn't have standard code formatter like gofmt, but there are some
third party checkers and formatters including, autopep8 and google/yapf.
There are also formmatters integrated in IDEs.

My concern is defining good edge cases for code formatter developers.
So my real question was: How many people prefer (or dislike) this rule is in code formatter?

If many people prefer this, could we have standard "Style guide for code formatter developers"
for rules too verbose to include PEP 8?

On Tuesday, March 31, 2015 at 5:34:40 PM UTC+9, Chris Angelico wrote:
On Tue, Mar 31, 2015 at 7:28 PM, INADA Naoki <> wrote:
> Benefit of this style is:
> 1) More consistent
> 2) No garbage diff just for just adding comma

So what you have there is a good reason for adopting this style. Is
there strong reason for mentioning it in PEP 8? Remember, every
recommendation in a style guide has a cost - too many rules and it
just becomes onerous, not to mention the increased likelihood of the
rule giving the wrong advice in some corner case (which leads
intelligent people to disregard the rule, and unintelligent checkers
to spew warnings which then have to be ignored - this is one of the
fundamental difficulties of scripting PEP 8 or any other style guide);
ideally, trust people to be intelligent, and don't enforce more than
you have to.

Python-ideas mailing list
Code of Conduct: