[issue2719] Backport next()
Raymond Hettinger
report at bugs.python.org
Wed Apr 30 08:04:32 CEST 2008
Raymond Hettinger <rhettinger at users.sourceforge.net> added the comment:
ISTM, the only value added by next(g) is that it replaces g.next() with
a more conventional spelling, g.__next__(). Since 2.6 still has g.next
(),I don't see how this backport adds value. It does however create a
second way to do it that will be confusing to some remaining in the 2.x
world. I think we should avoid double spellings in 2.6 except in cases
where the 2-to-3 converter would need help.
----------
nosy: +rhettinger
__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue2719>
__________________________________
More information about the Python-bugs-list
mailing list