Black – Uncompromising Python code formatter

Re:Black – Uncompromising Python code formatter by fjp on Friday May 17, 2019 @02:32PM (#19942253)

Our test pipeline fails any Python service trying to deploy if the black style check fails.

I was initially grumpy about my org adopting black because I preferred single quotes, but the level of standardization is a huge win in my book. I never even think about my code style anymore, I just write it and then run black.

[ Parent | on HN ]

Re:Black – Uncompromising Python code formatter by meowface on Friday May 17, 2019 @05:41PM (#19943830)

I've always been a double-quoter, in contrast to most Python devs I know/work with. After we standardized on black, I got some satisfaction seeing all of my coworkers bend to my will (/s).

[ Parent | on HN ]

Re:Black – Uncompromising Python code formatter by detaro on Friday May 17, 2019 @05:44PM (#19943850)

How narrow those two choices are! The correct answer is obviously to use single-quotes for keys and key-like cases and double-quotes for values. Make formatters impossible to write! (last sentence very /s, but that style actually exists)

[ Parent | on HN ]

Re:Black – Uncompromising Python code formatter by kbd on Saturday May 18, 2019 @01:27AM (#19945835)

That actually seems to be the de-facto Python style. Even Guido said at some point that that's his convention.

[ Parent | on HN ]

Re:Black – Uncompromising Python code formatter by witten on Friday May 17, 2019 @10:27PM (#19945222)

You can disable string normalization with Black, and then continue using single quotes all day. But then, yeah, you give up enforced standardization on that.

[ Parent | on HN ]

Re:Black – Uncompromising Python code formatter by prirun on Saturday May 18, 2019 @01:14PM (#19948501)

I started out double quoting but it takes longer to type Shift " vs ' so I switched early on.

[ Parent | on HN ]