[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map

2014-03-09 Thread Roundup Robot
Roundup Robot added the comment: New changeset 16c5d7c289c6 by Benjamin Peterson in branch '2.7': note that future_builtin's map is not quite like python 3's (closes #19363) http://hg.python.org/cpython/rev/16c5d7c289c6 -- nosy: +python-dev resolution: -> fixed stage: patch review -> co

[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map

2014-03-09 Thread Jessica McKellar
Jessica McKellar added the comment: Thanks for the patch, Gareth.Rees! The patch applies cleanly and the docs build cleanly with it. I visually inspected the addition in the built HTML docs and it looks good. => patch review -- keywords: +needs review -patch nosy: +jesstess stage: nee

[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map

2014-02-17 Thread Gareth Rees
Gareth Rees added the comment: Sorry about that; here it is. I had second thoughts about recommending zip() as an alternative (that would only work for cases where the None was constant; in other cases you might need lambda *args: args, but this seemed too complicated), so the note now says on

[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map

2014-02-15 Thread A.M. Kuchling
A.M. Kuchling added the comment: Gareth Rees: it doesn't look like you attached the patch mentioned in your 02/04 comment. -- nosy: +akuchling ___ Python tracker ___ ___

[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map

2014-02-08 Thread Nick Coghlan
Nick Coghlan added the comment: Switched to be a docs-only bug as Gareth suggested. -- assignee: rhettinger -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python, ncoghlan resolution: wont fix -> stage: committed/rejected -> needs patch ___

[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map

2014-02-04 Thread Gareth Rees
Gareth Rees added the comment: What about a documentation change instead? The future_builtins chapter in the standard library documentation could note the incompatibility. I've attached a patch which adds the following note to the documenta

[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map

2014-01-31 Thread Eric V. Smith
Eric V. Smith added the comment: I agree with Raymond: it would have been nice to do this, but it's too late. Closing. -- nosy: +eric.smith resolution: -> wont fix stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map

2013-12-22 Thread Raymond Hettinger
Raymond Hettinger added the comment: I agree with you in principle, but it is far too late in 2.7's development to take away a capability. -- ___ Python tracker ___

[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map

2013-10-24 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- assignee: -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map

2013-10-23 Thread Jon Clements
Changes by Jon Clements : -- nosy: +joncle ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map

2013-10-23 Thread Gareth Rees
New submission from Gareth Rees: In Python 2.7, future_builtins.map accepts None as its first (function) argument: Python 2.7.5 (default, Aug 1 2013, 01:01:17) >>> from future_builtins import map >>> list(map(None, range(3), 'ABC')) [(0, 'A'), (1, 'B'), (2, 'C')] But in Pytho