Black, the uncompromising Python code formatter, is stable

Re:Black, the uncompromising Python code formatter, is stable by hivacruz on Saturday January 29, 2022 @04:34PM (#30130752)

I understand that. And this is what I like in Black. But the single quotes thing is really up to debate. When you use it with other tools such as flake8 or pylint, you have to disable a bunch of things to make them work together because no one agrees on this point.

[ Parent | on HN ]

Re:Black, the uncompromising Python code formatter, is stable by j1elo on Saturday January 29, 2022 @04:45PM (#30130857)

I'm not a full time Python dev so I won't (can't) get into what choice has more merits. But there is this:

https://black.readthedocs.io/en/latest/the_black_code_style/...

Seen from outside, I think the double quotes are just the natural form of strings in lots of other places, at least in those that come from the same family than C (C++, Java, C#, Rust, just to name a few)

Also Prettier.js (which I'd call the "Black of JavaScript") also settled on double quotes. So we're left with a de facto consensus across programming languages as a whole, which kind of feels nice.

[ Parent | on HN ]

Re:Black, the uncompromising Python code formatter, is stable by historyforsale on Saturday January 29, 2022 @05:56PM (#30131464)

> When you use it with other tools such as flake8 or pylint, you have to disable a bunch of things to make them work together

Using Flake8 with Black requires only two configuration options [1], while Pylint requires three [2]. If you prefer to use Black with --line-length 79, then it's down to a single configuration option for Flake8 or two for Pylint.

[1]: https://black.readthedocs.io/en/latest/guides/using_black_wi...

[2]: https://black.readthedocs.io/en/latest/guides/using_black_wi...

[ Parent | on HN ]