You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a bug, in fact this is a feature called the "magic trailing comma". It was introduced via #826... so before the release of 19.10b0. When you want Black to always explode a collection literal even if it doesn't violate the line length limit, put a trailing comma and tada, Black will explode it. (Side-note: this feature is still needs more work to fully usable, e.g. nested collection literals are unsupported ATM). So if you remove the trailing comma, Black will collapse the function signature:
Describe the bug
Even when the line length would permit a single-line function definition, the args are separated from their surrounding parentheses
To Reproduce
black -l 1000
on this file always puts thef4
args on their own line:Expected behavior
Environment
Does this bug also happen on master?
Yes (via a clone/virtualenv test).
I assume this is not really a bug. So I must be missing some rule about arguments I cannot find in PEP8 or the
black
documentation.The text was updated successfully, but these errors were encountered: