On Dec 4, 5:45 pm, Andreas Waldenburger <[EMAIL PROTECTED]> wrote: > On Thu, 4 Dec 2008 11:52:38 -0600 [EMAIL PROTECTED] wrote: > > > > > >>> As you have probably guessed: nothing changed here. > > >>> Also see:http://www.python.org/dev/peps/pep-0666/ > > > >> What? Do you mean it's possible to mix tabs and spaces still? > > >> Why? > > > Daniel> Why not? > > > Because it has historically been a source of errors in a mixed > > development environment (people using text editors with different tab > > stops). Better to not allow them to be mixed. > > Whenever has it been a pythonic ideal to "not allow" stuff? You get > warnings. Everything else is up to you. > > /W > > -- > My real email address is constructed by swapping the domain with the > recipient (local part).
Python has "not allowed stuff" for a long time. For example, it disallows statements in lambdas. "Disallowing" is not bad. Disallowing bad practices (like mixing tabs and spaces) is actually good! I agree that the tab/space thing should be changed. Would it be too hard to make the parser see if the indentation is consistent in the whole file? This is a annoying source of problems, specially since you can't tell a whitespace from a tab just looking at it. And I personally disliked most of the changes (specially the ones on map and reduce). I hope functional programming doesn't get even more hindered in future releases, because I believe these changes only made Python weaker. Well, anyway, congratulations for everyone for Python 3 release. Some of the changes were a real improvement (like the Unicode sources). And I hope that, in the end, these changes help making Python a better language. -- http://mail.python.org/mailman/listinfo/python-list
