Black: An uncompromising Python code formatter

Re:Black: An uncompromising Python code formatter by kstrauser on Friday May 25, 2018 @02:27PM (#17156560)

That's the #1 complaint I have (and hear) about Black. Everything else, I can live with. And honestly, I can live with using double quotes everywhere, especially when I can type single quotes and then let it re-write them. It's just that they currently look really, really odd to me because that's not how Python is traditionally written.

[ Parent | on HN ]

Re:Black: An uncompromising Python code formatter by stevesimmons on Friday May 25, 2018 @08:11PM (#17159231)

I prefer a quoting convention of single quotes for text identifiers (as they rarely contain quotes) and double quotes for English text (because contractions are common). Thus:

    key['first_name'] 
    print("Isn't this clearer?")

[ Parent | on HN ]

Re:Black: An uncompromising Python code formatter by gvx on Friday May 25, 2018 @09:05PM (#17159471)

I generally follow this convention:

1. Any string literal that contains either ' xor " will be delimited by the other one. 2. For all other string literals, delimit by " if it's meant for human eyes only, delimit by ' if it's meant for computers as well.

[ Parent | on HN ]

Re:Black: An uncompromising Python code formatter by masklinn on Saturday May 26, 2018 @09:58AM (#17162040)

Same, though I'd word the first one as programmatic identifiers.

Adopted that from Erlang, where atoms are single-quoted and text strings are double-quoted.

[ Parent | on HN ]