Lines Matching full:split
47 - Adds `FORCE_MULTILINE_DICT` knob to ensure dictionaries always split,
64 - Don't split between two-word comparison operators: "is not", "not in", etc.
99 fits in its starting line, then the subexpression is not split (thus avoiding
107 - Lambda expressions shouldn't have an increased split penalty applied to the
120 set. `SPLIT_PENALTY_ARITHMETIC_OPERATOR` allows you to set the split penalty
133 those are likely to be split anyway. If we do split, it leads to horrible
138 a function call and doesn't fit on a single line, then it forces a split.
146 - `ALLOW_SPLIT_BEFORE_DEFAULT_OR_NAMED_ASSIGNS` allows us to split before
163 Split only if absolutely necessary.
165 - Ignore pseudo tokens when calculating split penalties.
168 dictionary entry is a container. If so, then it's probably split over
170 Therefore, we shouldn't enforce a split because of that.
171 - Increase split penalty around exponent operator.
182 computation of the line end when determining if it must split after the
188 style" option didn't work as advertised. Lines would split after the dots,
199 - Increase the split penalty for an if-expression.
201 split in a function call or other data literal.
228 function defs, etc... to split on all values, instead of maximizing the
231 - Improve the heuristic we use to determine when to split at the start of a
233 without wrapping. If not, then we split.
235 analyzed. This allows tuples to be split more rationally.
256 - Don't split ellipses.
265 operation: `**foo`. Take that into account and don't split after the
273 - Relax the split of a paren at the end of an if statement. With
274 `dedent_closing_brackets` option requires that it be able to split there.
284 split before the first argument in a function call.
285 - Split before the first argument in a function call if the arguments contain a
287 - Improve splitting of elements in a tuple. We want to split if there's a
291 - When calculating the split penalty for a "trailer", process the child nodes
294 - Don't enforce a split before a comment after the opening of a container if it
298 - Remove the penalty for a split before the first argument in a function call
303 - Added `SPLIT_BEFORE_EXPRESSION_AFTER_OPENING_PAREN` that enforces a split
306 - Split before the ending bracket of a comma-terminated tuple / argument list
309 - Prefer to split after a comma in an argument list rather than in the middle
314 - Take into account the "async" keyword when determining if we must split
324 - Option `ALLOW_SPLIT_BEFORE_DICT_VALUE` allows a split before a value. If
325 False, then it won't be split even if it goes over the column limit.
353 - Ensured comma-terminated tuples with multiple elements are split onto separate lines.
363 - Make sure to split after a comment even for "pseudo" parentheses.
373 - Split before a function call in a list if the full list isn't able to fit on
375 - Trying not to split around the '=' of a named assign.
376 - Changed split before the first argument behavior to ignore compound
378 - Changed coalesce brackets not to line split before closing bracket.
395 right-hand side. Split the arguments instead.
396 - We need to split a dictionary value if the first element is a comment anyway,
397 so don't force the split here. It's forced elsewhere.
412 - Split before all entries in a dict/set or list maker when comma-terminated,
420 - Don't perform a global split when a named assign is part of a function call
422 split here:
433 - Encourage the formatter to split at the beginning of an argument list instead
436 "not in" and other such operators don't want to have a split after it (or
441 - Keep type annotations intact as much as possible. Don't try to split the over
485 - It's not really more readable to split before a dictionary value if it's part
499 - Don't force a split before non-function call arguments.
501 on a single line shouldn't be split.
502 - Don't rely upon the original line break to determine if we should split
503 before the elements in a container. Especially split if there's a comment in
506 - If a nested data structure terminates in a comma, then split before the first
516 - Prefer to split before a terminating r-paren in an argument list if the line
518 - Split before the first key in a dictionary if the dictionary cannot fit on a
536 fit on a line by itself, then split before the call so that it won't be split
550 - It's okay to split in the middle of a dotted name if the whole expression is
555 - The splitting of arguments when comma terminated had a conflict. The split
566 - We split all of the arguments to a function call if there's a named argument.
567 In this case, we want to split after the opening bracket too. This makes
584 - Don't split an import list if it's not surrounded by parentheses.
588 - Added a knob (SPLIT_PENALTY_BEFORE_IF_EXPR) to adjust the split penalty
593 be split anyway.
598 - Don't split before a first element list argument as we would before a first
600 - Don't penalize when we must split a line.
605 - Prefer not to split after the opening of a subscript.
608 - When we're setting the split penalty for a continuous list, we don't want to
623 Instead, we need to carefully determine if the line is liabel to be split and
633 - If we split before a bitwise operator, then we assume that the programmer
634 knows what they're doing, more or less, and so we enforce a split before said
645 - Split after a bitwise operator when in PEP 8 mode.
697 - Add knob to indent the dictionary value if there is a split before it.
706 - When determining if we should split a dictionary's value to a new line, use
719 split before it.
729 - Add a knob to control whether import names are split after the first '('.
735 - Prefer to not split before the ending bracket of an atom. This produces
766 - Add bitwise operator splitting penalty and prefer to split before bitwise
771 - Split only at start of named assign.