News for hackers. Stuff that matters.
Re:Black: An uncompromising Python code formatter by eslaught on Friday May 25, 2018 @01:38PM (#17156107)
The phrasing "minutiae" is unfortunate because it makes it sound like the exact formatting is a matter of taste or doesn't matter. In my experience, there are always corner cases where either tools like these produce bad results. "Bad" isn't just some aesthetic property, it can mean the difference between being able to absorb the meaning of a block of code in 10 seconds, versus having to spend a minute taking it all in. Across a large body of code, those paper cuts really add up.

Personally, the only code formatter I've ever been really comfortable using is clang-format. And the reason is that they really try hard to get the corner cases right. Black might be fine, but I've been burned many times with other tools and in general would be reluctant to trust a tool like this without seeing what it does in practice to a large code base.

Re:Black: An uncompromising Python code formatter by Barrin92 on Friday May 25, 2018 @02:11PM (#17156414)
I think most people would agree that corner cases are an issue, but in large codebases the payoff of having a strong, unified standard provides a bigger payoff than spotty edge cases.

The larger the codebase and the more developers you have working on a project, the less important edge cases become and the more benefit you get from a common standard.

Re:Black: An uncompromising Python code formatter by ambivalence on Friday May 25, 2018 @01:55PM (#17156266)
For a large codebase that uses Black, you might want to look at PyPA/Warehouse or Fabric 2.