black seems to be where the community is going -- NumPy is planning on using it I think (?), and from a quick look it looks like pandas and scikit-learn already do or are headed in that direction. I'm sure @agramfort has opinions/experience to share here :)
It's possible to make a single big commit that makes all the changes, then add this to a git blame ignore file, which removes the potential blame pollution which (to me) was a big barrier to adoption.
So overall +1 for moving to black from me using whatever pre-commit hooks or whatever pandas and scikit-learn have done (despite me actually not particularly liking how black code ends up looking sometimes!).
I can volunteer to help people rebase or merge PRs that are broken by the changes if they need help.
cc @cbrnr who mentioned wanting longer than 79 char line length, this would be one way to do it.
EDIT:
blackseems to be where the community is going -- NumPy is planning on using it I think (?), and from a quick look it looks like pandas and scikit-learn already do or are headed in that direction. I'm sure @agramfort has opinions/experience to share here :)It's possible to make a single big commit that makes all the changes, then add this to a git blame ignore file, which removes the potential
blamepollution which (to me) was a big barrier to adoption.So overall +1 for moving to
blackfrom me using whatever pre-commit hooks or whatever pandas and scikit-learn have done (despite me actually not particularly liking how black code ends up looking sometimes!).I can volunteer to help people rebase or merge PRs that are broken by the changes if they need help.
cc @cbrnr who mentioned wanting longer than 79 char line length, this would be one way to do it.
EDIT: