[Python-Dev] defaultdict and on_missing() (original) (raw)
Raymond Hettinger raymond.hettinger at verizon.net
Wed Mar 1 00:28:38 CET 2006
- Previous message: [Python-Dev] defaultdict and on_missing()
- Next message: [Python-Dev] defaultdict and on_missing()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Greg Ewing]
I'd still like to see next(x) / x.next() in some form in 3.0 for the sake of consistency, though.
+1 on modifying next() in Py3.0 to accept the send argument.
-1 on the silly renaming to next and adding builtin.next(). We have len() because it applies to many different object types. In contrast, next() would apply only to iterables. Foolish consistency is a somewhat weak reason to add a built-in. Also, calls to it.next() need to be as fast as possible. Adding a layer of indirection through builtin.next() is a waste.
Raymond
- Previous message: [Python-Dev] defaultdict and on_missing()
- Next message: [Python-Dev] defaultdict and on_missing()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]