<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>rbanffy</author><text>&lt;p&gt;&lt;pre&gt;&lt;code&gt;  --style STYLE         specify formatting style: either a style name (for
                        example &amp;quot;pep8&amp;quot; or &amp;quot;google&amp;quot;), or the name of a file
                        with style settings. pep8 is the default.
&lt;/code&gt;&lt;/pre&gt;
&amp;gt; pep8 is the default.&lt;p&gt;I can breathe again.</text><parent_chain></parent_chain></comment><story><title>YAPF – A formatter for Python files</title><url>https://github.com/google/yapf</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>bkcooper</author><text>I&amp;#x27;m sure there are some cases where this is useful, but I&amp;#x27;m not really sold. The pitch at the beginning is &amp;quot;satisfying PEP 8 doesn&amp;#x27;t mean it looks good!&amp;quot; But then it seems most of the changes cleaned up in the code (indentation level, indents on split lines, spacing between operators) are just PEP 8 violations. I think you could find a more convincing demonstration.&lt;p&gt;The warning about choking on large data literals (which are probably one of the places where prettifying would be most useful, at least to me) also seems ominous.&lt;p&gt;edit: for my personal use, I tend to use flycheck with flake8 in emacs. This keeps me honest. Is the primary use case for something like this cleaning your own code or other people&amp;#x27;s?</text><parent_chain></parent_chain></comment><story><title>YAPF – A formatter for Python files</title><url>https://github.com/google/yapf</url></story>