Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update yapf to 0.19.0 #58

Closed
wants to merge 1 commit into from
Closed

Conversation

pyup-bot
Copy link
Contributor

There's a new version of yapf available.
You are currently using 0.16.2. I have updated it to 0.19.0

These links might come in handy: PyPI | Changelog

Changelog

0.19.0

Added

  • Added SPLIT_BEFORE_EXPRESSION_AFTER_OPENING_PAREN that enforces a split
    after the opening paren of an expression that's surrounded by parens.
    Changed
  • Split before the ending bracket of a comma-terminated tuple / argument list
    if it's not a single element tuple / arg list.
    Fixed
  • Prefer to split after a comma in an argument list rather than in the middle
    of an argument.
  • A non-multiline string may have newlines if it contains continuation markers
    itself. Don't add a newline after the string when retaining the vertical
    space.
  • Take into account the "async" keyword when determining if we must split
    before the first argument.
  • Increase affinity for "atom" arguments in function calls. This helps prevent
    lists from being separated when they don't need to be.
  • Don't place a dictionary argument on its own line if it's the last argument
    in the function call where that function is part of a builder-style call.
  • Append the "var arg" type to a star in a star_expr.

0.18.0

Added

  • Option ALLOW_SPLIT_BEFORE_DICT_VALUE allows a split before a value. If
    False, then it won't be split even if it goes over the column limit.
    Changed
  • Use spaces around the '=' in a typed name argument to align with 3.6 syntax.
    Fixed
  • Allow semicolons if the line is disabled.
  • Fix issue where subsequent comments at decreasing levels of indentation
    were improperly aligned and/or caused output with invalid syntax.
  • Fix issue where specifying a line range removed a needed line before a
    comment.
  • Fix spacing between unary operators if one is 'not'.
  • Indent the dictionary value correctly if there's a multi-line key.
  • Don't remove needed spacing before a comment in a dict when in "chromium"
    style.
  • Increase indent for continuation line with same indent as next logical line
    with 'async with' statement.

0.17.0

Added

  • Option NO_SPACES_AROUND_SELECTED_BINARY_OPERATORS prevents adding spaces
    around selected binary operators, in accordance with the current style guide.
    Changed
  • Adjust blank lines on formatting boundaries when using the --lines option.
  • Return 1 if a diff changed the code. This is in line with how GNU diff acts.
  • Add -vv flag to print out file names as they are processed
    Fixed
  • Corrected how DEDENT_CLOSING_BRACKETS and COALESCE_BRACKETS interacted.
  • Fix return value to return a boolean.
  • Correct vim plugin not to clobber edited code if yapf returns an error.
  • Ensured comma-terminated tuples with multiple elements are split onto separate lines.

0.16.3

Changed

  • Add filename information to a ParseError excetion.
    Fixed
  • A token that ends in a continuation marker may have more than one newline in
    it, thus changing its "lineno" value. This can happen if multiple
    continuation markers are used with no intervening tokens. Adjust the line
    number to account for the lines covered by those markers.
  • Make sure to split after a comment even for "pseudo" parentheses.

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 馃

@pyup-bot pyup-bot mentioned this pull request Oct 14, 2017
@hartym hartym closed this Nov 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants