On Sun, 23 Jul 2000, Fredrik Lundh wrote: > and for the record, I'm fully prepared to vote "no" on list comprehensions, > augumented assignments, range literals, and every trace of a new operator > that changes how python code is tokenized and parsed. I wouldn't go that far, but I'd vote "not until after 2.0" on everything except range literals. The idea being that range literals is something that has discussed since before I knew of Python (which is an objective measurement of course), and we've known what form they'll take for that long. List comprehensions, augmented assignments and new operators are something with an effect on the language that I personally cannot appreciate without more testing. > ...with two major releases with only a few weeks in between, I'm afraid we'll > see the usual "do we really need this?" rule being replaced with "what can we > add to make sure people know there's really a difference?". Well, I'm less cynical -- I do believe that we won't put any features without careful thought about the side effects of usability and readability. -- Moshe Zadka <moshez@math.huji.ac.il> There is no IGLU cabal. http://advogato.org/person/moshez
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4