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 # _Black_ compatible configurations
3 All of Black's changes are harmless (or at least, they should be), but a few do conflict
4 against other tools. It is not uncommon to be using other tools alongside _Black_ like
5 linters and type checkers. Some of them need a bit of tweaking to resolve the conflicts.
6 Listed below are _Black_ compatible configurations in various formats for the common
9 **Please note** that _Black_ only supports the TOML file format for its configuration
10 (e.g. `pyproject.toml`). The provided examples are to only configure their corresponding
11 tools, using **their** supported file formats.
15 [isort](https://pypi.org/p/isort/) helps to sort and format imports in your Python code.
16 _Black_ also formats imports, but in a different way from isort's defaults which leads
17 to conflicting changes.
23 include_trailing_comma = True
25 use_parentheses = True
26 ensure_newline_before_comments = True
30 ### Why those options above?
32 _Black_ wraps imports that surpass `line-length` by moving identifiers into their own
33 indented line. If that still doesn't fit the bill, it will put all of them in separate
34 lines and put a trailing comma. A more detailed explanation of this behaviour can be
35 [found here](https://github.com/psf/black/blob/master/docs/the_black_code_style.md#how-black-wraps-lines).
37 isort's default mode of wrapping imports that extend past the `line_length` limit is
41 from third_party import (lib1, lib2, lib3,
45 This style is incompatible with _Black_, but isort can be configured to use a different
46 wrapping mode called "Vertical Hanging Indent" which looks like this:
49 from third_party import (
57 This style is _Black_ compatible and can be achieved by `multi-line-output = 3`. Also,
58 as mentioned above, when wrapping long imports _Black_ puts a trailing comma and uses
59 parentheses. isort should follow the same behaviour and passing the options
60 `include_trailing_comma = True` and `use_parentheses = True` configures that.
62 The option `force_grid_wrap = 0` is just to tell isort to only wrap imports that surpass
63 the `line_length` limit.
65 Finally, isort should be told to wrap imports when they surpass _Black_'s default limit
66 of 88 characters via `line_length = 88` as well as
67 `ensure_newline_before_comments = True` to ensure spacing import sections with comments
68 works the same as with _Black_.
70 **Please note** `ensure_newline_before_comments = True` only works since isort >= 5 but
71 does not break older versions so you can keep it if you are running previous versions.
72 If only isort >= 5 is used you can add `profile = black` instead of all the options
73 since [profiles](https://timothycrosley.github.io/isort/docs/configuration/profiles/)
74 are available and do the configuring for you.
79 <summary>.isort.cfg</summary>
84 include_trailing_comma = True
86 use_parentheses = True
87 ensure_newline_before_comments = True
94 <summary>setup.cfg</summary>
99 include_trailing_comma = True
101 use_parentheses = True
102 ensure_newline_before_comments = True
109 <summary>pyproject.toml</summary>
113 multi_line_output = 3
114 include_trailing_comma = true
116 use_parentheses = true
117 ensure_newline_before_comments = true
124 <summary>.editorconfig</summary>
128 multi_line_output = 3
129 include_trailing_comma = True
131 use_parentheses = True
132 ensure_newline_before_comments = True
140 [Flake8](https://pypi.org/p/flake8/) is a code linter. It warns you of syntax errors,
141 possible bugs, stylistic errors, etc. For the most part, Flake8 follows
142 [PEP 8](https://www.python.org/dev/peps/pep-0008/) when warning about stylistic errors.
143 There are a few deviations that cause incompatibilities with _Black_.
152 ### Why those options above?
154 In some cases, as determined by PEP 8, _Black_ will enforce an equal amount of
155 whitespace around slice operators. Due to this, Flake8 will raise
156 `E203 whitespace before ':'` warnings. Since this warning is not PEP 8 compliant, Flake8
157 should be configured to ignore it via `extend-ignore = E203`.
159 When breaking a line, _Black_ will break it before a binary operator. This is compliant
161 [April 2016](https://github.com/python/peps/commit/c59c4376ad233a62ca4b3a6060c81368bd21e85b#diff-64ec08cc46db7540f18f2af46037f599).
162 There's a disabled-by-default warning in Flake8 which goes against this PEP 8
163 recommendation called `W503 line break before binary operator`. It should not be enabled
164 in your configuration.
166 Also, as like with isort, flake8 should be configured to allow lines up to the length
167 limit of `88`, _Black_'s default. This explains `max-line-length = 88`.
172 <summary>.flake8</summary>
183 <summary>setup.cfg</summary>
194 <summary>tox.ini</summary>
206 [Pylint](https://pypi.org/p/pylint/) is also a code linter like Flake8. It has the same
207 checks as flake8 and more. In particular, it has more formatting checks regarding style
208 conventions like variable naming. With so many checks, Pylint is bound to have some
209 mixed feelings about _Black_'s formatting style.
214 disable = C0330, C0326
218 ### Why those options above?
220 When _Black_ is folding very long expressions, the closing brackets will
221 [be dedented](https://github.com/psf/black#how-black-wraps-lines).
224 ImportantClass.important_method(
225 exc, limit, lookup_lines, capture_locals, callback
229 Although, this style is PEP 8 compliant, Pylint will raise
230 `C0330: Wrong hanging indentation before block (add 4 spaces)` warnings. Since _Black_
231 isn't configurable on this style, Pylint should be told to ignore these warnings via
234 Also, since _Black_ deals with whitespace around operators and brackets, Pylint's
235 warning `C0326: Bad whitespace` should be disabled using `disable = C0326`.
237 And as usual, Pylint should be configured to only complain about lines that surpass `88`
238 characters via `max-line-length = 88`.
243 <summary>pylintrc</summary>
247 disable = C0330, C0326
256 <summary>setup.cfg</summary>
262 [pylint.messages_control]
263 disable = C0330, C0326
269 <summary>pyproject.toml</summary>
272 [tool.pylint.messages_control]
273 disable = "C0330, C0326"
276 max-line-length = "88"