All patches and comments are welcome. Please squash your changes to logical
commits before using git-format-patch and git-send-email to
patches@git.madduck.net.
If you'd read over the Git project's submission guidelines and adhered to them,
I'd be especially grateful.
1 # Installation and Usage
5 *Black* can be installed by running `pip install black`.
9 To get started right away with sensible defaults:
15 ### Command line options
17 Some basics about the command line help, `black --help`:
20 Usage: black [OPTIONS] [SRC]...
22 The uncompromising code formatter.
25 -l, --line-length INTEGER How many character per line to allow. [default:
27 --check Don't write back the files, just return the
28 status. Return code 0 means nothing would
29 change. Return code 1 means some files would be
30 reformatted. Return code 123 means there was an
32 --fast / --safe If --fast given, skip temporary sanity checks.
34 --version Show the version and exit.
35 --help Show this message and exit.
38 `Black` is a well-behaved Unix-style command-line tool:
40 * it does nothing if no sources are passed to it;
41 * it will read from standard input and write to standard output if `-`
42 is used as the filename;
43 * it only outputs messages to users on standard error;
44 * exits with code 0 unless an internal error occured (or `--check` was
47 ## Important note about the pre-release of Black
49 *Black* can already successfully format itself and the standard library.
50 It also sports a decent test suite. However, it is still very new.
51 Things will probably be wonky for a while. This is made explicit by the
52 "Alpha" trove classifier, as well as by the "a" in the version number.
53 What this means for you is that **until the formatter becomes stable,
54 you should expect some formatting to change in the future**.
56 Also, as a temporary safety measure, *Black* will check that the
57 reformatted code still produces a valid AST that is equivalent to the
58 original. This slows it down. If you're feeling confident, use