> > Yeah, it's just a pain that it's been deployed in Python 2.2 since > > last December, and by the time 2.3 is out it will probably have been > > at least a full year. Worse, 2.2 is voted to be Python-in-a-Tie, > > giving that particular idiom a very long lifetime. I simply don't > > think we can break compatibility that easily. Remember the endless > > threads we've had about the pace of change and stability. We have to > > live with warts, alas. And this is a pretty minor one if you ask me. > > Is this a Pronouncement, or are we still waiting on the results of the > survey? That is my current opinion. I'm waiting for the results of the survey to see if I'll be swayed (but I don't think it's likely). > Note that several people have suggested a multi-release > strategy for fixing this problem; does that make any difference? Such a big gun for such a minor problem. --Guido van Rossum (home page: http://www.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