Mark writes - > This is not a desirable trait in a "first programming language" for > teaching computer science.
Because we need to teach the programmers early on that they are not responsible for their mistakes? It's the tool's fault. Not sure why that line of reasoning gets to me the way it does. Although the point you raise certainly gets enough attention - for example a recent 140 message thread on python-list. And certainly I am not criticizing for laying it on the table here. In fact on such a thread a few months ago, I got upset with Alex Martelli for roughly bashing someone who was pressing this point. (and let him know so) But you should realize how strongly some folks who understand Python deeply feel about the issue. No declarations. Alex goes a step further, feeling that "global" in Python is a serious wart because it is itself a declaration. Being the easy going guy that I am ;), I am usually OK with Python as it happens to be, and usually get a little confused (and upset) when I am informed (by the defenders of the faith, no less) that I am being complacent, and that things need to change - again. At this point, most of the things that I would think would be most difficult to understand about Python - for someone coming to it fresh - would be the artifacts of transitions and changes. i.e. new style and old style classes, list comprehension vs generator comprehensions, div old vs div new, @property, and I am sure many others that don't come to me off the top of my head. All theses changes are understandable, standalone. But sometimes I do feel that the people who want them, are greedy for them. And like to sell them as freebies. No change is a freebie at this stage. Art _______________________________________________ Edu-sig mailing list Edu-sig@python.org http://mail.python.org/mailman/listinfo/edu-sig
