[Python-3000] PEP: rename it.next() to it.next(), add a next() built-in (original) (raw)
Josiah Carlson jcarlson at uci.edu
Tue Mar 6 21:05:13 CET 2007
- Previous message: [Python-3000] PEP: rename it.next() to it.__next__(), add a next() built-in
- Next message: [Python-3000] PEP: rename it.next() to it.__next__(), add a next() built-in
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"Guido van Rossum" <guido at python.org> 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
- Previous message: [Python-3000] PEP: rename it.next() to it.__next__(), add a next() built-in
- Next message: [Python-3000] PEP: rename it.next() to it.__next__(), add a next() built-in
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]