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/23/75/c374517c09e31bf22d3b3f156d73e0f38d08e29b2afdd607cef5f1e10aa9
14 DISTFILE[1]= yapf-0.40.1-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.40.1.dist-info
28 [PY310].RUN_DEPENDS_ON= python-importlib-metadata:single:py310
29 python-platformdirs:single:py310
30 python-tomli:single:py310
31 [PY310].USES_ON= python:py310,wheel
33 [PY311].RUN_DEPENDS_ON= python-importlib-metadata:single:v11
34 python-platformdirs:single:v11
35 python-tomli:single:v11
36 [PY311].USES_ON= python:v11,wheel
38 [FILE:2624:descriptions/desc.single]
54 Most of the current formatters for Python --- e.g., autopep8, and pep8ify
56 are made to remove lint errors from code. This has some obvious
58 For instance, code that conforms to the PEP 8 guidelines may not be
59 reformatted. But it doesn't mean that the code looks good.
61 YAPF takes a different approach. It's based off of `'clang-format'
63 ang.llvm.org/docs/ClangFormat.html>`_, developed by Daniel Jasper. In
65 the algorithm takes the code and reformats it to the best formatting that
66 conforms to the style guide, even if the original code didn't violate the
67 style guide. The idea is also similar to the ['gofmt'] tool for the Go
68 programming language: end all holy wars about
69 formatting - if the whole codebase of a project is simply piped through
71 whenever modifications are made, the style remains consistent throughout
73 project and there's no point arguing about style in every code review.
75 The ultimate goal is that the code YAPF produces is as good as the code
77 programmer would write if they were following the style guide. It takes
79 some of the drudgery of maintaining your code.
83 YAPF is not an official Google product (experimental or otherwise), it
85 just code that happens to be owned by Google.
92 To install YAPF from PyPI:
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.
135 positional arguments:
136 files reads from stdin when no files are specified.
142 b8bfc1f280949153e795181768ca14ef43d7312629a06c43e7abd279323af313 250316 yapf-0.40.1-py3-none-any.whl