Tracy R Reed wrote: > Christopher Smith wrote: >> I of course *know* you are totally wrong about TAB, but I'd settle for >> a language that just chose a side and forced everyone to stick with >> one way. Python's approach let's them mix and it's just a recipe for >> disaster. > > While I tend to agree with you, so far I have not once in several years > of playing with Python run into such a situation. > >
It does occasionally happen that there is an undesired effect on semantics that makes it past the compile phase. Frequently enough that they have a -tt option as well as pychecker/pylint to ferret out those potential problems. I have gotten pretty comfortable with python whitespace, and I think any programmer can live with it even when s/he doesn't like it. The cut-n-paste problem is real, but I have always found a way. It is annoying, though. The only other thing I can gripe about is that the lack of a visible end-block delimiter another annoyance in editing and debugging. I suspect both of these could be fixed by fancier presentation tricks (highlighting, color, etc). Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
