Brett Cannon added the comment:
I never bothered to mention the iter* methods in the HOWTO, and since it
becomes very obvious very fast to tweak them I'm not going to worry about it
and add more complexity to the doc.
--
resolution: -> wont fix
status: open -> closed
Josh Rosenberg added the comment:
I think the suggestion is intended for "how do I keep Python 2 semantics in
Python 3?", not "how can I write my Python 2 code so it will run equivalently
in Python 3?"
It wouldn't be a bad idea to point out that you can adopt Py3 semantics
initially so as to
New submission from Brett Cannon:
In Python 2.6 and newer you can import future_builtins and use everything from
there. In Python 2.5 it should be itertools.imap(). This is much cleaner than
the current suggestion at
https://docs.python.org/2/howto/pyporting.html#update-map-for-imbalanced-inpu
