On Thu, 4 Dec 2008 15:49:46 -0600 [EMAIL PROTECTED] wrote: > > Andreas> Whenever has it been a pythonic ideal to "not allow" > Andreas> stuff? You get warnings. Everything else is up to you. > > It's more than warnings. With properly crafted combinations of > spaces and tabs you can get code which looks like it has a certain > indentation to the human observer but which looks like it has > different indentation (and thus different semantics) to the byte code > compiler. There is often no warning. > I just looked at "python --help", it seems that there is no warning per default.
My point is: If you mix tabs and spaces in a way that breaks code, you'll find out pretty easily, because your program will not work. It's your choice, and I think it's pretty nice that Python lets you choose. After all, some people are of the "indentation for structure, spaces for alignment" faction. Why make their life harder? /W -- My real email address is constructed by swapping the domain with the recipient (local part). -- http://mail.python.org/mailman/listinfo/python-list
