[Python-3000] PEP: rename it.next() to it.next(), add a next() built-in (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Tue Mar 6 00:52:20 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 ]
Aahz wrote:
I'm +0 on operator.next() relative to builtin next().
I'm -0.7. Classifying next() as an operator doesn't seem right -- what "operator" does it correspond to?
Unlike all the other functions in the operator module, there is no piece of syntax that corresponds directly to what next() would do. There's the for-loop, but that does considerably more.
-- Greg
- 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 ]