News for hackers. Stuff that matters.
Re:Black: An uncompromising Python code formatter by 0xffff2 on Friday May 25, 2018 @12:45PM (#17155455)
I'm fine with ceding control right up until the formatter does something I don't like for no good reason. For languages like Rust, where there is a single format convention that is closely tied to the language (via rstfmt), I am okay with this kind of forced standard. For something like Python, C++, or Java where there isn't a single "winner" for format guidelines, there's virtually no chance that I would embrace something like this.
Re:Black: An uncompromising Python code formatter by revfried on Friday May 25, 2018 @12:50PM (#17155512)
A little bit of a catch 22 you think?

C++ has clangfmt.

Black has a good momentum right now it very well might be the clear winner in a few months

Re:Black: An uncompromising Python code formatter by 0xffff2 on Friday May 25, 2018 @02:40PM (#17156699)
I don't think it's a catch-22 at all. Either the language has an official style guide (C#) and/or formatter (Rust, Go), or it doesn't (C++, Java). Given that black doesn't even seem to comply with PEP-8, I don't consider it acceptable.

I use clang format because it gives me full control over the style I cede control to it because it happens that I can express all of my personal minutiae of hand formatting in clang format rules. In contrast, I currently am writing Java in VS Code, and the Java formatting plugin doesn't give me an easy way to change its rules, so I disabled it entirely.

Re:Black: An uncompromising Python code formatter by ambivalence on Friday May 25, 2018 @02:51PM (#17156793)
> black doesn't even seem to comply with PEP-8

That is just not true. Where does Black not conform to PEP 8?

Re:Black: An uncompromising Python code formatter by zbentley on Friday May 25, 2018 @06:51PM (#17158793)
> right up until the formatter does something I don't like for no good reason.

Hand-formatting. You are describing formatting code by hand.