Depends on the mood.

Whatever your place defines as a standard. I’ve seen ugly code in C, JavaScript, Java, etc., that uses them all over the place because they’re not mandatory.

If you don’t have consistent indenting, your code looks like copy/paste from several sources; but if you do have consistent indenting, then the indenting of Python is a non-issue.

No one will ever know. That is my editor’s job. XD

Per the Linux kernel coding style:

Tabs are 8 characters, and thus indentations are also 8 characters. There are heretic movements that try to make indentations 4 (or even 2!) characters deep, and that is akin to trying to define the value of PI to be 3.

I’m rather partial to five myself but only when I’m feeling fancy.

Yes

Haskell has the choice of both indentation based and brackets for things like do blocks, but most people use indentation based cause it’s the norm and looks cleaner

White space sensitive languages are evil.

I’m not saying I don’t understand them. I’m saying the syntax is terrible. Compare it to Ruby (or any other modern language) and it’s abundantly clear.

python (uses syntax not available in any other top 25 language)

print([j**2 for j in [2, 3, 4, 5]]) # => [4, 9, 16, 25]

ruby (normal chain syntax with map)

puts [2, 3, 4, 5].map{|j| j**2}

even kotlin is more readable, even though you have to convert to a double and back kotlin

val list = listOf(1,2,3,4)
println(list.map{it.toDouble().pow(2.0).toInt()})

For nested cases it’s even more apparent:

python

digits = [1, 2, 3]
chars = ['a', 'b', 'c']    
print([str(d)+ch for d in digits for ch in chars if d >= 2 if ch == 'a'])    
# => ['2a', '3a']

ruby

digits = [1, 2, 3]
chars = ['a', 'b', 'c']   
digits.product(chars).select{ |d, ch| d >= 2 && ch == 'a' }.map(&:join)

kotlin

val digits = listOf(1, 2, 3)
val chars = listOf('a', 'b', 'c')
println(digits.flatMap { d ->
    chars.filter { ch -> d >= 2 && ch == 'a' }.map { ch -> "${d}${ch}" }})

just from a base level, you have to read the middle of the comprehension first, then the end, then the beginning. It’s a completely backwards way to write and read code. unlike other languages that use a ‘functional’ approach, where it’s chained methods or pipes, etc. Even Elixir, which does have list comprehensions, reads and writes in the proper order:

elixir

for x <- 0..100, x * x > 3, do: x * 2

The concept of a list comprehenshion is sinple but syntax is awful, as if Yoda was writing a for loop. “x for x in y it is, hmm yes”.

and that indentation defaults in decent editors are usually language dependent. I’m not familiar with these editors, but… come on - if they use one default for all files, OP should use a better tool.

Yes, but I don’t normally program in python, so I never did. When I had to, I never thought of changing it (it wasn’t for long anyways and was less of a thought out decision to do programming in vim)