Bump black from 22.12.0 to 23.1.0

[dependabot]

Bumps black from 22.12.0 to 23.1.0.

Release notes

Sourced from black's releases.

23.1.0

Highlights

This is the first release of 2023, and following our stability policy, it comes with a number of improvements to our stable style, notably improvements to empty line handling and the removal of redundant parentheses in several contexts.

There are also many changes to the preview style; try out black --preview and give us feedback to help us set the stable style for next year.

In addition to style changes, Black now automatically infers the supported Python versions from your pyproject.toml file, removing the need to set Black's target versions separately.

Stable style

• Introduce the 2023 stable style, which incorporates most aspects of last year's preview style (#3418). Specific changes:
  • Enforce empty lines before classes and functions with sticky leading comments (#3302) (22.12.0)
  • Reformat empty and whitespace-only files as either an empty file (if no newline is present) or as a single newline character (if a newline is present) (#3348) (22.12.0)
  • Correctly handle trailing commas that are inside a line's leading non-nested parens (#3370) (22.12.0)
  • --skip-string-normalization / -S now prevents docstring prefixes from being normalized as expected (#3168) (since 22.8.0)
  • When using --skip-magic-trailing-comma or -C, trailing commas are stripped from subscript expressions with more than 1 element (#3209) (22.8.0)
  • Fix a string merging/split issue when a comment is present in the middle of implicitly concatenated strings on its own line (#3227) (22.8.0)
  • Docstring quotes are no longer moved if it would violate the line length limit (#3044, #3430) (22.6.0)
  • Parentheses around return annotations are now managed (#2990) (22.6.0)
  • Remove unnecessary parentheses around awaited objects (#2991) (22.6.0)
  • Remove unnecessary parentheses in with statements (#2926) (22.6.0)
  • Remove trailing newlines after code block open (#3035) (22.6.0)
  • Code cell separators #%% are now standardised to # %% (#2919) (22.3.0)
  • Remove unnecessary parentheses from except statements (#2939) (22.3.0)
  • Remove unnecessary parentheses from tuple unpacking in for loops (#2945) (22.3.0)
  • Avoid magic-trailing-comma in single-element subscripts (#2942) (22.3.0)
• Fix a crash when a colon line is marked between # fmt: off and # fmt: on (#3439)

Preview style

• Format hex codes in unicode escape sequences in string literals (#2916)
• Add parentheses around if-else expressions (#2278)
• Improve performance on large expressions that contain many strings (#3467)
• Fix a crash in preview style with assert + parenthesized string (#3415)
• Fix crashes in preview style with walrus operators used in function return annotations and except clauses (#3423)
• Fix a crash in preview advanced string processing where mixed implicitly concatenated regular and f-strings start with an empty span (#3463)
• Fix a crash in preview advanced string processing where a standalone comment is placed before a dict's value (#3469)
• Fix an issue where extra empty lines are added when a decorator has # fmt: skip applied or there is a standalone comment between decorators (#3470)
• Do not put the closing quotes in a docstring on a separate line, even if the line is too long (#3430)
• Long values in dict literals are now wrapped in parentheses; correspondingly unnecessary parentheses around short values in dict literals are now removed; long string lambda values are now wrapped in parentheses (#3440)
• Fix two crashes in preview style involving edge cases with docstrings (#3451)
• Exclude string type annotations from improved string processing; fix crash when the return type annotation is stringified and spans across multiple lines (#3462)
• Wrap multiple context managers in parentheses when targeting Python 3.9+ (#3489)
• Fix several crashes in preview style with walrus operators used in with statements or tuples (#3473)
• Fix an invalid quote escaping bug in f-string expressions where it produced invalid code. Implicitly concatenated f-strings with different quotes can now be merged or quote-normalized by changing the quotes used in expressions. (#3509)

... (truncated)

Changelog

Sourced from black's changelog.

23.1.0

Highlights

This is the first release of 2023, and following our stability policy, it comes with a number of improvements to our stable style, including improvements to empty line handling, removal of redundant parentheses in several contexts, and output that highlights implicitly concatenated strings better.

There are also many changes to the preview style; try out black --preview and give us feedback to help us set the stable style for next year.

In addition to style changes, Black now automatically infers the supported Python versions from your pyproject.toml file, removing the need to set Black's target versions separately.

Stable style

• Introduce the 2023 stable style, which incorporates most aspects of last year's preview style (#3418). Specific changes:
  • Enforce empty lines before classes and functions with sticky leading comments (#3302) (22.12.0)
  • Reformat empty and whitespace-only files as either an empty file (if no newline is present) or as a single newline character (if a newline is present) (#3348) (22.12.0)
  • Implicitly concatenated strings used as function args are now wrapped inside parentheses (#3307) (22.12.0)
  • Correctly handle trailing commas that are inside a line's leading non-nested parens (#3370) (22.12.0)
  • --skip-string-normalization / -S now prevents docstring prefixes from being normalized as expected (#3168) (since 22.8.0)
  • When using --skip-magic-trailing-comma or -C, trailing commas are stripped from subscript expressions with more than 1 element (#3209) (22.8.0)
  • Implicitly concatenated strings inside a list, set, or tuple are now wrapped inside parentheses (#3162) (22.8.0)
  • Fix a string merging/split issue when a comment is present in the middle of implicitly concatenated strings on its own line (#3227) (22.8.0)
  • Docstring quotes are no longer moved if it would violate the line length limit (#3044, #3430) (22.6.0)
  • Parentheses around return annotations are now managed (#2990) (22.6.0)
  • Remove unnecessary parentheses around awaited objects (#2991) (22.6.0)
  • Remove unnecessary parentheses in with statements (#2926) (22.6.0)
  • Remove trailing newlines after code block open (#3035) (22.6.0)
  • Code cell separators #%% are now standardised to # %% (#2919) (22.3.0)
  • Remove unnecessary parentheses from except statements (#2939) (22.3.0)
  • Remove unnecessary parentheses from tuple unpacking in for loops (#2945) (22.3.0)
  • Avoid magic-trailing-comma in single-element subscripts (#2942) (22.3.0)

... (truncated)

Commits

• b0d1fba Prepare release 23.1.0 (#3536)
• 69ca0a4 Infer target version based on project metadata (#3219)
• c4bd2e3 Draft for Black 2023 stable style (#3418)
• 226cbf0 Fix unsafe cast in linegen.py w/ await yield handling (#3533)
• f4ebc68 Upgrade isort (#3534)
• 6407ebb Remove Python version in the_basics.md (#3528)
• 196b1f3 Fix black --help output for --python-cell-magics option to be reproducibl...
• d950f15 Update document now that paren wrapping CMs on Python 3.9+ is implemented (#3...
• a36878e Fix an invalid quote escaping bug in f-string expressions (#3509)
• eabff67 Format hex code in unicode escape sequences in string literals (#2916)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[return42]

@dalf to pass black QG I added b4c80d9 before the black update. What do you think should we merge b4c80d9 ?

IMO: the changing code formatting is overly petty and is starting to get annoying --> If the author can't give emphasis through paragraphs, then the code becomes unreadable and the actual goal of code formatting was to ensure readable code.

[return42]

This is what we hear often from black ..

We will not be adding a toggle for this. I'm still not convinced that this should be reverted, however, I realize this is a disruptive change. The recommended workflow is to pin Black to ~= 22.0 so you continue to only get the 2022 stable code style.

• Remove newline after code block open psf/black#3035 (comment)

We are not alone:

• Allow a single newline after opening blocks, possibly via an option setting psf/black#3551 (comment)

And this is the future:

• Don't insert extra blank lines at the start of an indent psf/black#3089

Long story told short: If the author is unable to use paragraphs to add emphasis, the code becomes unreadable and the goal of code formatting (readability) is lost.

Black's dictator style comes from a very academical point of view and makes black more and more unusable in real project that have a history. The diffs created by this tool are huge and make branching and merging unnecessarily difficult --> The merge conflicts created by this tool unnecessarily increase the frequency of merge errors.

We should stop updating this tool and think about replacing it with a more suitable tool.

@dependabot ignore this dependency

[dependabot]

OK, I won't notify you about black again, unless you re-open this PR. 😢

[dependabot]

OK, I won't notify you about black again, unless you re-open this PR. 😢