Bump black from 20.8b1 to 21.7b0

[dependabot-preview]

Bumps black from 20.8b1 to 21.7b0.

Release notes

Sourced from black's releases.

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)
• Fixed option usage when using the --code flag (#2259)
• Do not call uvloop.install() when Black is used as a library (#2303)
• Added --required-version option to require a specific version to be running (#2300)
• Fix incorrect custom breakpoint indices when string group contains fake f-strings (#2311)
• Fix regression where R prefixes would be lowercased for docstrings (#2285)
• Fix handling of named escapes (\N{...}) when --experimental-string-processing is used (#2319)

21.5b2

Black

• A space is no longer inserted into empty docstrings (#2249)
• Fix handling of .gitignore files containing non-ASCII characters on Windows (#2229)
• Respect .gitignore files in all levels, not only root/.gitignore file (apply .gitignore rules like git does) (#2225)
• Restored compatibility with Click 8.0 on Python 3.6 when LANG=C used (#2227)
• Add extra uvloop install + import support if in python env (#2258)
• Fix --experimental-string-processing crash when matching parens are not found (#2283)
• Make sure to split lines that start with a string operator (#2286)

... (truncated)

Changelog

Sourced from black's changelog.

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)
• Fixed option usage when using the --code flag (#2259)
• Do not call uvloop.install() when Black is used as a library (#2303)
• Added --required-version option to require a specific version to be running (#2300)
• Fix incorrect custom breakpoint indices when string group contains fake f-strings (#2311)
• Fix regression where R prefixes would be lowercased for docstrings (#2285)
• Fix handling of named escapes (\N{...}) when --experimental-string-processing is used (#2319)

Integrations

• The official Black action now supports choosing what version to use, and supports the major 3 OSes. (#1940)

21.5b2

Black

... (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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)