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 # The (future of the) Black code style
4 Changes to this document often aren't tied and don't relate to releases of
5 _Black_. It's recommended that you read the latest version available.
8 ## Using backslashes for with statements
10 [Backslashes are bad and should be never be used](labels/why-no-backslashes) however
11 there is one exception: `with` statements using multiple context managers. Before Python
12 3.9 Python's grammar does not allow organizing parentheses around the series of context
15 We don't want formatting like:
18 with make_context_manager1() as cm1, make_context_manager2() as cm2, make_context_manager3() as cm3, make_context_manager4() as cm4:
19 ... # nothing to split on - line too long
22 So _Black_ will, when we implement this, format it like this:
26 make_context_manager1() as cm1, \
27 make_context_manager2() as cm2, \
28 make_context_manager3() as cm3, \
29 make_context_manager4() as cm4 \
31 ... # backslashes and an ugly stranded colon
34 Although when the target version is Python 3.9 or higher, _Black_ will, when we
35 implement this, use parentheses instead since they're allowed in Python 3.9 and higher.
37 An alternative to consider if the backslashes in the above formatting are undesirable is
38 to use {external:py:obj}`contextlib.ExitStack` to combine context managers in the
42 with contextlib.ExitStack() as exit_stack:
43 cm1 = exit_stack.enter_context(make_context_manager1())
44 cm2 = exit_stack.enter_context(make_context_manager2())
45 cm3 = exit_stack.enter_context(make_context_manager3())
46 cm4 = exit_stack.enter_context(make_context_manager4())
52 Experimental, potentially disruptive style changes are gathered under the `--preview`
53 CLI flag. At the end of each year, these changes may be adopted into the default style,
54 as described in [The Black Code Style](./index.rst). Because the functionality is
55 experimental, feedback and issue reports are highly encouraged!
57 ### Improved string processing
59 _Black_ will split long string literals and merge short ones. Parentheses are used where
60 appropriate. When split, parts of f-strings that don't need formatting are converted to
61 plain strings. User-made splits are respected when they do not exceed the line length
62 limit. Line continuation backslashes are converted into parenthesized strings.
63 Unnecessary parentheses are stripped. The stability and status of this feature is
64 tracked in [this issue](https://github.com/psf/black/issues/2188).
66 ### Improved empty line management
68 1. _Black_ will remove newlines in the beginning of new code blocks, i.e. when the
69 indentation level is increased. For example:
74 print("The line above me will be deleted!")
81 print("The line above me will be deleted!")
84 This new feature will be applied to **all code blocks**: `def`, `class`, `if`,
85 `for`, `while`, `with`, `case` and `match`.
87 2. _Black_ will enforce empty lines before classes and functions with leading comments.
92 # Leading sticky comment
103 # Leading sticky comment
108 ### Improved parentheses management
110 _Black_ will format parentheses around return annotations similarly to other sets of
111 parentheses. For example:
117 def foo() -> looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong:
129 looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong
134 And, extra parentheses in `await` expressions and `with` statements are removed. For
138 with ((open("bla.txt")) as f, open("x")):
142 await (asyncio.sleep(1))
148 with open("bla.txt") as f, open("x"):
153 await asyncio.sleep(1)