4 ms·
yapf is developed using an internal Google coding style. Please don't hold it against the project :-) Once you get used to the style, the code of yapf is very c
by eliben 12y ago
yapf is developed using an internal Google coding style. Please don't hold it against the project :-) Once you get used to the style, the code of yapf is very consistent in terms of style (it was formatted with yapf itself!) and should be easy to understand & work with.
It does support the PEP8 style out of the box, however.
- geoelectric 12y agoI think you've conflated Chromium style with Google style. https://www.chromium.org/chromium-os/python-style-guidelines https://www.chromium.org/chromium-os/python-style-guidelines ...is 2 spaces. http://google-styleguide.googlecode.com/svn/trunk/pyguide.html http://google-styleguide.googlecode.com/svn/trunk/pyguide.ht... ...is 4 spaces. The other difference is naming style. Chromium uses CapWords instead of snake_case. Edit: https://news.ycombinator.com/item?id=1311799 https://news.ycombinator.com/item?id=1311799 ^ that notes that you're referring to an internal style guide. Their external guide (which is the one I'd think I'd be following) is more PEP8-y. You might consider renaming your "google" to "google-internal." But since Chromium appears to be the remaining big external-facing project using the old internal style, I'd suggest chromium vs. google vs. pep8. That would make more sense to the wider audience.