1 # Buildsheet autogenerated by ravenadm tool -- Do not edit.
7 SDESC[py37]= Formatter for Python code (PY37)
8 SDESC[py38]= Formatter for Python code (PY38)
10 CONTACT= Python_Automaton[python@ironwolf.systems]
13 SITES[main]= PYPIWHL/c1/5d/d84677fe852bc5e091739acda444a9b6700ffc6b11a21b00dd244c8caef0
14 DISTFILE[1]= yapf-0.30.0-py2.py3-none-any.whl:main
19 OPTIONS_AVAILABLE= PY38 PY37
20 OPTIONS_STANDARD= none
21 VOPTS[py37]= PY38=OFF PY37=ON
22 VOPTS[py38]= PY38=ON PY37=OFF
24 DISTNAME= yapf-0.30.0.dist-info
28 [PY37].BUILD_DEPENDS_ON= python-pip:single:py37
29 [PY37].USES_ON= python:py37,wheel
31 [PY38].BUILD_DEPENDS_ON= python-pip:single:py38
32 [PY38].USES_ON= python:py38,wheel
34 [FILE:2641:descriptions/desc.single]
48 Most of the current formatters for Python --- e.g., autopep8, and pep8ify
50 are made to remove lint errors from code. This has some obvious
52 For instance, code that conforms to the PEP 8 guidelines may not be
53 reformatted. But it doesn't mean that the code looks good.
55 YAPF takes a different approach. It's based off of `'clang-format'
57 ang.llvm.org/docs/ClangFormat.html>`_, developed by Daniel Jasper. In
59 the algorithm takes the code and reformats it to the best formatting that
60 conforms to the style guide, even if the original code didn't violate the
61 style guide. The idea is also similar to the ['gofmt'] tool for the Go
62 programming language: end all holy wars about
63 formatting - if the whole codebase of a project is simply piped through
65 whenever modifications are made, the style remains consistent throughout
67 project and there's no point arguing about style in every code review.
69 The ultimate goal is that the code YAPF produces is as good as the code
71 programmer would write if they were following the style guide. It takes
73 some of the drudgery of maintaining your code.
75 Try out YAPF with this [online demo].
79 YAPF is not an official Google product (experimental or otherwise), it
81 just code that happens to be owned by Google.
88 To install YAPF from PyPI:
94 (optional) If you are using Python 2.7 and want to enable multiprocessing:
100 YAPF is still considered in "alpha" stage, and the released version may
102 often; therefore, the best way to keep up-to-date with the latest
104 is to clone this repository.
106 Note that if you intend to use YAPF as a command-line tool rather than as a
107 library, installation is not necessary. YAPF supports being run as a
109 by the Python interpreter. If you cloned/unzipped YAPF into DIR, it's
112 .. code-block:: shell
114 $ PYTHONPATH=DIR python DIR/yapf [options] ...
119 YAPF supports Python 2.7 and 3.6.4+. (Note that some Python 3 features may
121 to parse with Python versions before 3.6.4.)
123 YAPF requires the code it formats to be valid Python for the version YAPF
125 runs under. Therefore, if you format Python 3 code with YAPF, run YAPF
127 under Python 3 (and similarly for Python 2).
134 usage: yapf [-h] [-v] [-d | -i] [-r | -l START-END] [-e PATTERN]
138 3abf61ba67cf603069710d30acbc88cfe565d907e16ad81429ae90ce9651e0c9 190268 yapf-0.30.0-py2.py3-none-any.whl