1 # Buildsheet autogenerated by ravenadm tool -- Do not edit.
6 VARIANTS= py27 py35 py36
7 SDESC[py35]= Formatter for Python code. (PY 35)
8 SDESC[py36]= Formatter for Python code. (PY 36)
9 SDESC[py27]= Formatter for Python code. (PY 27)
11 CONTACT= Python_Automaton[python@ironwolf.systems]
14 SITES[main]= PYPI/y/yapf
15 DISTFILE[1]= yapf-0.17.0.tar.gz:main
21 OPTIONS_AVAILABLE= PY27 PY35 PY36
22 OPTIONS_STANDARD= none
23 VOPTS[py35]= PY27=OFF PY35=ON PY36=OFF
24 VOPTS[py36]= PY27=OFF PY35=OFF PY36=ON
25 VOPTS[py27]= PY27=ON PY35=OFF PY36=OFF
33 [PY35].USES_ON= python:py35
35 [PY36].USES_ON= python:py36
37 [PY27].USES_ON= python:py27
39 [FILE:2987:descriptions/desc.single]
44 .. image:: https://badge.fury.io/py/yapf.svg
45 :target: http://badge.fury.io/py/yapf
48 .. image:: https://travis-ci.org/google/yapf.svg?branch=master
49 :target: https://travis-ci.org/google/yapf
52 .. image:: https://coveralls.io/repos/google/yapf/badge.svg?branch=master
53 :target: https://coveralls.io/r/google/yapf?branch=master
60 Most of the current formatters for Python --- e.g., autopep8, and pep8ify ---
61 are made to remove lint errors from code. This has some obvious limitations.
62 For instance, code that conforms to the PEP 8 guidelines may not be
63 reformatted. But it doesn't mean that the code looks good.
65 YAPF takes a different approach. It's based off of 'clang-format', developed by
66 Daniel Jasper. In essence, the algorithm takes the code and reformats it to the
67 best formatting that conforms to the style guide, even if the original code
68 didn't violate the style guide. The idea is also similar to the 'gofmt' tool for
69 the Go programming language: end all holy wars about formatting - if the whole
70 codebase of a project is simply piped through YAPF whenever modifications are
71 made, the style remains consistent throughout the project and there's no point
72 arguing about style in every code review.
74 The ultimate goal is that the code YAPF produces is as good as the code that a
75 programmer would write if they were following the style guide. It takes away
76 some of the drudgery of maintaining your code.
80 YAPF is not an official Google product (experimental or otherwise), it is
81 just code that happens to be owned by Google.
89 To install YAPF from PyPI:
95 (optional) If you are using Python 2.7 and want to enable multiprocessing:
101 YAPF is still considered in "alpha" stage, and the released version may change
102 often; therefore, the best way to keep up-to-date with the latest development
103 is to clone this repository.
105 Note that if you intend to use YAPF as a command-line tool rather than as a
106 library, installation is not necessary. YAPF supports being run as a directory
107 by the Python interpreter. If you cloned/unzipped YAPF into ``DIR``, it's
112 $ PYTHONPATH=DIR python DIR/yapf [options] ...
118 YAPF supports Python 2.7 and 3.4.1+.
120 YAPF requires the code it formats to be valid Python for the version YAPF itself
121 runs under. Therefore, if you format Python 3 code with YAPF, run YAPF itself
122 under Python 3 (and similarly for Python 2).
130 usage: yapf [-h] [-v] [-d | -i] [-r | -l START-END] [-e PATTERN]
131 [--style STYLE] [--style-help] [--no-local-style] [-p]
134 Formatter for Python code.
136 positional arguments:
143 5472f4c95ab9b9fe9f5bf74ece3c986bfafa1f98ad9e1e296d4c35d291c97856 116736 yapf-0.17.0.tar.gz