Bump black from 20.8b1 to 21.8b0

[dependabot[bot]]

Bumps black from 20.8b1 to 21.8b0.

Release notes

Sourced from black's releases.

21.8b0

Black

• Add support for formatting Jupyter Notebook files (#2357)
• Move from appdirs dependency to platformdirs (#2375)
• Present a more user-friendly error if .gitignore is invalid (#2414)
• The failsafe for accidentally added backslashes in f-string expressions has been hardened to handle more edge cases during quote normalization (#2437)
• Avoid changing a function return type annotation's type to a tuple by adding a trailing comma (#2384)
• Parsing support has been added for unparenthesized walruses in set literals, set comprehensions, and indices (#2447).
• Pin setuptools-scm build-time dependency version (#2457)
• Exclude typing-extensions version 3.10.0.1 due to it being broken on Python 3.10 (#2460)

Blackd

• Replace sys.exit(-1) with raise ImportError as it plays more nicely with tools that scan installed packages (#2440)

Integrations

• The provided pre-commit hooks no longer specify language_version to avoid overriding default_language_version (#2430)

21.7b0

Black

• Configuration files using TOML features higher than spec v0.5.0 are now supported (#2301)
• Add primer support and test for code piped into black via STDIN (#2315)
• Fix internal error when FORCE_OPTIONAL_PARENTHESES feature is enabled (#2332)
• Accept empty stdin (#2346)
• Provide a more useful error when parsing fails during AST safety checks (#2304)

Docker

• Add new latest_release tag automation to follow latest black release on docker images (#2374)

Integrations

• The vim plugin now searches upwards from the directory containing the current buffer instead of the current working directory for pyproject.toml. (#1871)
• The vim plugin now reads the correct string normalization option in pyproject.toml (#1869)
• The vim plugin no longer crashes Black when there's boolean values in pyproject.toml (#1869)

21.6b0

Black

• Fix failure caused by fmt: skip and indentation (#2281)
• Account for += assignment when deciding whether to split string (#2312)
• Correct max string length calculation when there are string operators (#2292)

... (truncated)

Changelog

Sourced from black's changelog.

21.8b0

Black

• Add support for formatting Jupyter Notebook files (#2357)
• Move from appdirs dependency to platformdirs (#2375)
• Present a more user-friendly error if .gitignore is invalid (#2414)
• The failsafe for accidentally added backslashes in f-string expressions has been hardened to handle more edge cases during quote normalization (#2437)
• Avoid changing a function return type annotation's type to a tuple by adding a trailing comma (#2384)
• Parsing support has been added for unparenthesized walruses in set literals, set comprehensions, and indices (#2447).
• Pin setuptools-scm build-time dependency version (#2457)
• Exclude typing-extensions version 3.10.0.1 due to it being broken on Python 3.10 (#2460)

Blackd

• Replace sys.exit(-1) with raise ImportError as it plays more nicely with tools that scan installed packages (#2440)

Integrations

• The provided pre-commit hooks no longer specify language_version to avoid overriding default_language_version (#2430)

21.7b0

Black

• Configuration files using TOML features higher than spec v0.5.0 are now supported (#2301)
• Add primer support and test for code piped into black via STDIN (#2315)
• Fix internal error when FORCE_OPTIONAL_PARENTHESES feature is enabled (#2332)
• Accept empty stdin (#2346)
• Provide a more useful error when parsing fails during AST safety checks (#2304)

Docker

• Add new latest_release tag automation to follow latest black release on docker images (#2374)

Integrations

• The vim plugin now searches upwards from the directory containing the current buffer instead of the current working directory for pyproject.toml. (#1871)
• The vim plugin now reads the correct string normalization option in pyproject.toml (#1869)
• The vim plugin no longer crashes Black when there's boolean values in pyproject.toml

... (truncated)

Commits

• See full diff 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)

[codeclimate[bot]]

Code Climate has analyzed commit 798a19b7 and detected 0 issues on this pull request.

View more on Code Climate.

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.