You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What about using black now that it is stable and a standard tool?
By using Black, you agree to cede control over minutiae of hand-formatting. In return, Black gives you speed, determinism, and freedom from pycodestyle nagging about formatting. You will save time and mental energy for more important matters.
Personally, I'd make it checked by CI... but I'm also OK to convert the code base and fix it once in a while.
What do you think?
The text was updated successfully, but these errors were encountered:
The issue when partly using black is ending with PRs polluted by some reformatting.
Now, in practice with the current activity of the project, that shouldn't be a big deal...
And even less if it is set on save in the IDE or as a pre-commit hook.
So as I said, it's OK for me not to have it in the CI.
Finally it will also break the whole previous open PR
What about using
black
now that it is stable and a standard tool?Personally, I'd make it checked by CI... but I'm also OK to convert the code base and fix it once in a while.
What do you think?
The text was updated successfully, but these errors were encountered: