> I'm really quite torn. The more rational side of my brain agrees with > this position. OTOH, it just doesn't make much sense to me to add > list comprehensions and augmented assignments (and a raft of other new > features) in a 2.1 release. Seems like 2.0 is where all the new stuff > should go, with 2.x's as bug fix releases. That was my reasoning too -- which is why I was quite torn too at lunch (not just by the menu choices). I believe earlier we discussed how in particular list comprehensions don't affect much else, so even if they are broken, that shouldn't affect the stability of all the other new code that we put in, and I don't see how they could hold up the 2.0final release much. I'm much less sure about augmented assignments -- that's one big sucker of a patch! > Think of all the new features added in 1.5.2 (a /micro/ release for > gawds' sake). In retrospect, that was nutty. Yesh... > ah-hell-let's-release-a-1.6-after-all-ly y'rs, That's an in-joke :-) --Guido van Rossum (home page: http://dinsdale.python.org/~guido/)
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