That's a bit rich. There are other conventions in programming that you can't depend on technically but serve a real purpose. Identifier naming and comments are the first that come to mind.
If a language gives you a choice of token that has no semantic distinction then different people will adopt different semantics by convention.
As an aside, calling a tool "opinionated" is code for "my conventions are better than yours". That's fine if I don't have any conventions or I can't decide, but if I have decided, then it's just offensive.
So I don't read "opinionated" to necessarily mean "better than your opinions"; it's more like "makes decisions for you so you can avoid the cost of debating them."
But I can buy the argument that just having a single auto-enforced rule improves consistency and that has greater benefits than the somewhat vague distinction that is not enforced.
Yes. It's pretty much the only formatting style point that we don't have automated.
> As for number of lines after imports, how is a lack of enforcement there stopping you from using the tool?
Our current automated linting enforces it, but Black doesn't always reformat it, so we might get linter errors from Black formatted code.
Alright, fair enough!
> Black doesn't always reformat it, so we might get linter errors from Black formatted code.
Well, as long as it doesn't add new linter errors, that should be fine, do you disagree?
There are always going to be suboptimal formattings and missing transformations but as long as the situation gets better automatically on average and can be further improved with minimal manual input, you should be fine.
As for number of lines after imports, how is a lack of enforcement there stopping you from using the tool? Black enforces one line but is fine if you put two (on module level). In general, if you give up on the tool due to a missing rule, you end up having to manually enforce tens of other rules that you'd otherwise be free from.