What’s the material consequence of this lack of uniformity? When a new Python developer joins a team, is it painful or costly to accommodate their stylistic preferences? I see a single standard as a nice to have, but as long as the language has adequate tooling with reasonable defaults and quality linting, this just doesn’t seem like a big deal. Curious to learn first hand experience of those that switched from Python to Go…

I’ve found it’s nice for detecting people who care about unimportant things.

I can’t imagine ever picking a language based on this feature and seems weird to even mention it.

This has never caused me a minute of headache and the only time I care is when conflicting styles are used in the same file.

I always thought it was kind of dumb of Go to care about this but don’t care enough to affect my language choice. I don’t use Go but am open if it’s a fit for a project.

I like that Python has that variability and let’s developer make decisions as they see fit.

I don’t want to talk to people about tabs and spaces unless we’re already friends and having a few beers.

In candor I dabbled in Go in 2016 and found the community leaders arrogant and rude. I hope the community has evolved since then to expect more from leaders, but would need to see evidence of this before touching Go voluntarily again.

I've used a good dozen languages and I don't know the "community leaders" of any of those.

The biggest issue I've felt with Python formatting is you run into build/versioning issues that basically never happen with gofmt. Also, some tools don't do everything you need, and you need multiple, like having to combine isort and black.