News for hackers. Stuff that matters.
Re:Black: An uncompromising Python code formatter by prawl on Friday May 25, 2018 @10:43PM (#17159889)
This isn't a vast majority by any stretch of the imagination.
Re:Black: An uncompromising Python code formatter by jhall1468 on Saturday May 26, 2018 @09:30AM (#17161903)
The overwhelming response here saying use single quotes begs to differ.
Re:Black: An uncompromising Python code formatter by ambivalence on Saturday May 26, 2018 @11:31AM (#17162559)
That's not how this works. All the people who are just happy or indifferent about double quotes don't comment about it. And some of the ones that aren't happy about it commented here multiple times.

Judging from the additional stars on GitHub, and projects that just migrated (pytest!), I'd say there's a very vocal minority which is very attached to single quotes.

Re:Black: An uncompromising Python code formatter by jhall1468 on Monday May 28, 2018 @12:17PM (#17173210)
> Judging from the additional stars on GitHub, and projects that just migrated (pytest!), I'd say there's a very vocal minority which is very attached to single quotes.

Accuse me of selection bias. Immediately use even more biased selection bias.

Re:Black: An uncompromising Python code formatter by pkilgore on Saturday May 26, 2018 @12:43PM (#17162939)
Selection bias is real here.

I thought dbl quotes smart for all the reasons in the readme. Me commenting 'this is great' is just noise on HN, and discouraged by the rules. Never take self-selected anything as truth, especially comments (tweets/posts/voluntary votes)

Re:Black: An uncompromising Python code formatter by aldanor on Monday May 28, 2018 @08:11AM (#17171992)
This is all subjective unless some data is collected. I could say with just as much confidence that all of the major Python projects I've seen or contributed to use single quotes -- e.g. numpy or pandas.