black and pre-commit fight each other

[jaraco]

The skeleton, attempting to follow best practices, requires three different versions of black installed:

• black installed in the test suite to validate the syntax during test runs, defined in the tests requirements based on PyPI releases.
• black installed in the developer's environment to apply the syntax changes, defined by the developer across any number of projects.
• black installed by pre-commit to prevent the developer from committing invalid syntax, defined in pre-commit yaml based on Git rev refs.

As you can see, there are three different versions of black defined in three different places, one at a different scope than the others (user vs project), and using different version schemes (git refs vs. releases).

And because black changes what is considered valid syntax on a release-by-release basis, there's no reliable way to maintain consistency short of pinning to a specific version and updating that pinned version across projects and environments.

Even installing the "latest" "stable" version of all dependencies (as is currently defined), I've run into issues getting everything in sync.

There's got to be a better way.

[jaraco]

In pre-commit/pre-commit#1748, I learned that there's no intention to support a "latest" concept, so the best way to manage this for now is to repeatedly update the version here using the "autoupdate" command, and Anthony recommends to consider using https://pre-commit.ci instead.