So you can have a local, and a team config. So at time of commit the code rules your team has selected are enforced. So if I looked at my code, on GitHub, it would look as expected by the team.
I love such formatters and wish they were even more widespread. In many cases, I really want consistency above all and it's so dang hard to achieve that without an opinionated formatter. If the formatters isn't opinionated enough, it just leads to countless human enforced rules that waste time (and lead to an understandable chorus of "why can't the formatter just do that for meeeee").
Yeah but outside of that where the code is implemented or in a documentation, tabs are still easier to look through. And it does look pretty as long as there aren't too many nested functions.
Not any standard (and actually not at all something to do for real), but try it, it works
def magic(a, b, c):
if a > 0:
if b > 0:
if c > 0:
return 'All positive'
return 'Not all positive'
print(magic(1,2,3))
print(magic(-1,1,2))
print(magic(1,-1,0))
print(magic(-1,-1,-2))
(you should be able to verify I used both tab and spaces f*cking bad way in this example, like I described)
Output:
All positive
Not all positive
Not all positive
Not all positive
** Process exited - Return Code: 0 **
Press Enter to exit terminal
That's really interesting. So does that mean the interpreter just checks whether the current line is more indented, less indented, or equal vs. the preceding, without caring by how much?