I like it 👍

I've seen more and more Python projects adopt black such that it now seems very natural style to me. I think it makes the process easier for new contributors as they won't need to stress or think about the project's coding style. Instead just let the tool handle it.

As a mere infrequent outside contributor, I'm for it.

Provided it is just run automatically over new code, I could see this as being a time saver. On the other hand, will new contributors be confused about why their code has rearranged itself?

Note that you'd also want to add this to requirements.txt

Provided it is just run automatically over new code, I could see this as being a time saver. On the other hand, will new contributors be confused about why their code has rearranged itself?

You do need to run the command, it's not in a pre-commit hook or anything (but if they wished they could create one, or add it to their editor on save). But it's just a pip install black && black <dir>. It will fix lots of potential flake8 errors too.

On the CI, black --check --diff will show any fixes it would have made in case someone wants to make the changes manually and without the tool.

Note that you'd also want to add this to requirements.txt

Added.

If no other comments, let's merge this and I'll make a new PR for the other directories.

Consider merging in #3898 first, before the changes from this PR make a simple revert unviable.

Yep, good idea.