>>>Yuk! How impossible to read.
>>In vfp I agree, as the closing code line is needed and should be seen as a bracket.
>>
>>But in Python the "deeper" indent level marks the code as belonging to the previous control structure:
>>it sounds ridicolous on first read, but after a few H it feels like a great idea.
>>
>>Yupp, Tab/blsnks can be a major issue<g>.
>>
>>regards
>>
>>thomas
>
>I'm not coding in Python, but I'm aware of that issue and I can't say I'm fond of it. Making invisible characters have significance in controlling execution is pretty stupid, IMHO.

Similar to my first reaction - but reading other people's code is *very* easy in that language. If you view it from another POV, it only needs an editor marking/mapping meaningful invisible characters or - even better - arranging identation on the same lines as the compiler "understands" the source (as they have multiline strings it is not totally trivial). Give it an honest chance before making a judgement - the fact that identation is used in nearly every language even if control structure is governed by the constructs needing their complement (as in if-endif) or some block markers (like {} or begin-end) hints that it might be helpful<g>.

regards

thomas