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)
9 HOMEPAGE= https://github.com/google/yapf
10 CONTACT= Python_Automaton[python@ironwolf.systems]
13 SITES[main]= PYPIWHL/32/ec/531851d561ecb656bd58dc102338d0aa07e086788f351c63a9f6b8a00fe6
14 DISTFILE[1]= yapf-0.33.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.33.0.dist-info
28 [PY310].RUN_DEPENDS_ON= python-tomli:single:py310
29 [PY310].USES_ON= python:py310,wheel
31 [PY311].RUN_DEPENDS_ON= python-tomli:single:v11
32 [PY311].USES_ON= python:v11,wheel
34 [FILE:2599: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.
77 YAPF is not an official Google product (experimental or otherwise), it
79 just code that happens to be owned by Google.
86 To install YAPF from PyPI:
92 (optional) If you are using Python 2.7 and want to enable multiprocessing:
98 YAPF is still considered in "alpha" stage, and the released version may
100 often; therefore, the best way to keep up-to-date with the latest
102 is to clone this repository.
104 Note that if you intend to use YAPF as a command-line tool rather than as a
105 library, installation is not necessary. YAPF supports being run as a
107 by the Python interpreter. If you cloned/unzipped YAPF into DIR, it's
110 .. code-block:: shell
112 $ PYTHONPATH=DIR python DIR/yapf [options] ...
117 YAPF supports Python 3.7+.
119 YAPF requires the code it formats to be valid Python for the version YAPF
121 runs under. So if formatting 3.7 Python run YAPF under 3.7
128 usage: yapf [-h] [-v] [-d | -i | -q] [-r | -l START-END] [-e PATTERN]
129 [--style STYLE] [--style-help] [--no-local-style] [-p]
133 Formatter for Python code.
138 4c2b59bd5ffe46f3a7da48df87596877189148226ce267c16e8b44240e51578d 200892 yapf-0.33.0-py2.py3-none-any.whl