1 # Buildsheet autogenerated by ravenadm tool -- Do not edit.
7 SDESC[py310]= Formatter for Python code (3.10)
8 SDESC[v11]= Formatter for Python code (3.11)
10 CONTACT= Python_Automaton[python@ironwolf.systems]
13 SITES[main]= PYPIWHL/47/88/843c2e68f18a5879b4fbf37cb99fbabe1ffc4343b2e63191c8462235c008
14 DISTFILE[1]= yapf-0.32.0-py2.py3-none-any.whl:main
19 OPTIONS_AVAILABLE= PY310 PY311
20 OPTIONS_STANDARD= none
21 VOPTS[py310]= PY310=ON PY311=OFF
22 VOPTS[v11]= PY310=OFF PY311=ON
24 DISTNAME= yapf-0.32.0.dist-info
28 [PY310].USES_ON= python:py310,wheel
30 [PY311].USES_ON= python:v11,wheel
32 [FILE:2695:descriptions/desc.single]
46 Most of the current formatters for Python --- e.g., autopep8, and pep8ify
48 are made to remove lint errors from code. This has some obvious
50 For instance, code that conforms to the PEP 8 guidelines may not be
51 reformatted. But it doesn't mean that the code looks good.
53 YAPF takes a different approach. It's based off of `'clang-format'
55 ang.llvm.org/docs/ClangFormat.html>`_, developed by Daniel Jasper. In
57 the algorithm takes the code and reformats it to the best formatting that
58 conforms to the style guide, even if the original code didn't violate the
59 style guide. The idea is also similar to the ['gofmt'] tool for the Go
60 programming language: end all holy wars about
61 formatting - if the whole codebase of a project is simply piped through
63 whenever modifications are made, the style remains consistent throughout
65 project and there's no point arguing about style in every code review.
67 The ultimate goal is that the code YAPF produces is as good as the code
69 programmer would write if they were following the style guide. It takes
71 some of the drudgery of maintaining your code.
75 YAPF is not an official Google product (experimental or otherwise), it
77 just code that happens to be owned by Google.
84 To install YAPF from PyPI:
90 (optional) If you are using Python 2.7 and want to enable multiprocessing:
96 YAPF is still considered in "alpha" stage, and the released version may
98 often; therefore, the best way to keep up-to-date with the latest
100 is to clone this repository.
102 Note that if you intend to use YAPF as a command-line tool rather than as a
103 library, installation is not necessary. YAPF supports being run as a
105 by the Python interpreter. If you cloned/unzipped YAPF into DIR, it's
108 .. code-block:: shell
110 $ PYTHONPATH=DIR python DIR/yapf [options] ...
115 YAPF supports Python 2.7 and 3.6.4+. (Note that some Python 3 features may
117 to parse with Python versions before 3.6.4.)
119 YAPF requires the code it formats to be valid Python for the version YAPF
121 runs under. Therefore, if you format Python 3 code with YAPF, run YAPF
123 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]
136 8fea849025584e486fd06d6ba2bed717f396080fd3cc236ba10cb97c4c51cf32 190236 yapf-0.32.0-py2.py3-none-any.whl