Black is a really cool, if not the Python code formatter. It reduces whitespace, visual clutter, and helps teams to produce the same code style.
I had problems in 2 PRs during the integration tests because of "whitespace" in another file (that I did not edit).
This could be solved by just using black.
If you are ok with that, I could create a simple PR with black as dev requirement, and reformatting all files using black .
But I recommend that you, @jonathan-s do that, as it touches much code in one commit, and in git blameit would look like I had written all the code :-)
Black is a really cool, if not the Python code formatter. It reduces whitespace, visual clutter, and helps teams to produce the same code style.
I had problems in 2 PRs during the integration tests because of "whitespace" in another file (that I did not edit). This could be solved by just using black.
If you are ok with that, I could create a simple PR with black as dev requirement, and reformatting all files using
black .But I recommend that you, @jonathan-s do that, as it touches much code in one commit, and ingit blameit would look like I had written all the code :-)