"Guido van Rossum" <[EMAIL PROTECTED]> wrote: > Having now read this entire thread I am going to accept Ping's PEP. > Adding the sentinel argument to the next() builtin was what did it for > me: it neatly solves the problem if having to catch that StopIteration > in 99% of the cases.
Have you read the post by Thomas Wouters in regards to .next() vs. .__next__() [1]? The idea is that methods that *shouldn't* be called from user code explicitly have generally received __magic__ methods, while methods that have uses-cases for being called directly get nonmagic methods. He (and I believe most everyone) is in favor of some two-argument builtin or otherwise named next(interator, default=), it's the bulk renaming of .next -> .__next__ that is the real point of contention (with non-iterator .next methods, .next instance variables, etc.) - Josiah [1] http://mail.python.org/pipermail/python-3000/2007-March/006010.html _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
