Benjamin Peterson [EMAIL PROTECTED] added the comment:
This has been done.
--
nosy: +benjamin.peterson
resolution: - duplicate
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2336
New submission from Brett Cannon [EMAIL PROTECTED]:
PEP 3114 needs to be backported. Most likely the best approach is to
backport the next() built-in but to have it call next() on the iterator
instead of __next__(). That should hopefully minimize breakage while
allowing for moving over to the
Raymond Hettinger [EMAIL PROTECTED] added the comment:
I don't think this should be backported. It leaves Py2.6 with a
confused mess of protocols. The 2-to-3 transformation is simple.
Backporting doesn't add value.
--
nosy: +rhettinger
__
Tracker
Changes by Brett Cannon [EMAIL PROTECTED]:
--
priority: immediate - urgent
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2336
__
___
Python-bugs-list mailing list
