[Python-3000] PEP: rename it.next() to it.next(), add a next() built-in (original) (raw)
python at rcn.com python at rcn.com
Mon Mar 5 20:29:55 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 ]
[Ka-Ping]
Title: Renaming iterator.next() to iterator.next() ======================================================
[Josiah]
It sounds and reads just fine, though I'm -1 on the change if only because 1) it adds a builtin, 2) it renames a protocol method, making it potentially difficult and/or buggy to write forward or backward compatible code, 3) it smells like gratuitous breakage.
And, more importantly, it is butt-ugly.
Raymond
- 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 ]