On Tue, Jul 16, 2002 at 09:29:55PM -0400, Guido van Rossum wrote: | > An aside on "next" vs. "__next__": | > | > As far as i know, "next" is the only implicitly-called method of | > an internal protocol that has no underscores. It's a little late | > to fix the name of "next" in Python 2, though it might be worth | > considering for Python 3. | | Yup. I regret this too. | But yes, it's too late to change now. I don't think it is too late. 90% ++ of the python code base out there doesn't use iterators yet... people are still wrapping their minds around it to see how they can use it in their applications. If it was publicly stated that this could be "fixed" in the next version I don't think that it would hurt. These things happen, and sometimes its best to "roll back". Programmers understand this. Best, Clark -- Clark C. Evans Axista, Inc. http://www.axista.com 800.926.5525 XCOLLA Collaborative Project Management Software
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