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.
3 ### 18.3a4 (unreleased)
5 * automatic detection of deprecated Python 2 forms of print statements
6 and exec statements in the formatted file (#49)
8 * use proper spaces for complex expressions in default values of typed
9 function arguments (#60)
11 * only return exit code 1 when --check is used (#50)
13 * don't remove single trailing commas from square bracket indexing
16 * don't omit whitespace if the previous factor leaf wasn't a math
19 * omit extra space in kwarg unpacking if it's the first argument (#46)
21 * omit extra space in [Sphinx auto-attribute comments](http://www.sphinx-doc.org/en/stable/ext/autodoc.html#directive-autoattribute)
27 * don't remove single empty lines outside of bracketed expressions
30 * added ability to pipe formatting from stdin to stdin (#25)
32 * restored ability to format code with legacy usage of `async` as
35 * even better handling of numpy-style array indexing (#33, again)
40 * changed positioning of binary operators to occur at beginning of lines
41 instead of at the end, following [a recent change to PEP8](https://github.com/python/peps/commit/c59c4376ad233a62ca4b3a6060c81368bd21e85b)
44 * ignore empty bracket pairs while splitting. This avoids very weirdly
45 looking formattings (#34, #35)
47 * remove a trailing comma if there is a single argument to a call
49 * if top level functions were separated by a comment, don't put four
50 empty lines after the upper function
52 * fixed unstable formatting of newlines with imports
54 * fixed unintentional folding of post scriptum standalone comments
55 into last statement if it was a simple statement (#18, #28)
57 * fixed missing space in numpy-style array indexing (#33)
59 * fixed spurious space after star-based unary expressions (#31)
66 * only put trailing commas in function signatures and calls if it's
67 safe to do so. If the file is Python 3.6+ it's always safe, otherwise
68 only safe if there are no `*args` or `**kwargs` used in the signature
71 * fixed invalid spacing of dots in relative imports (#6, #13)
73 * fixed invalid splitting after comma on unpacked variables in for-loops
76 * fixed spurious space in parenthesized set expressions (#7)
78 * fixed spurious space after opening parentheses and in default
81 * fixed spurious space after unary operators when the operand was
82 a complex expression (#15)
87 * first published version, Happy 🍰 Day 2018!
91 * date-versioned (see: https://calver.org/)