From: Benjamin Peterson <benjamin@python.org>
Date: Sun, 9 Mar 2014 19:01:09 +0000 (-0500)
Subject: note that future_builtin's map is not quite like python 3's (closes #19363)
X-Git-Tag: v2.7.7rc1~144
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=84f323eae727387eedbfc0f701dbc6b82f1bcf21;p=python

note that future_builtin's map is not quite like python 3's (closes #19363)

Patch by Gareth Rees.
---

diff --git a/Doc/library/future_builtins.rst b/Doc/library/future_builtins.rst
index 04f20526ca..62392eb4b6 100644
--- a/Doc/library/future_builtins.rst
+++ b/Doc/library/future_builtins.rst
@@ -50,6 +50,11 @@ Available builtins are:
 
    Works like :func:`itertools.imap`.
 
+   .. note::
+
+      In Python 3, :func:`map` does not accept ``None`` for the
+      function argument.
+
 .. function:: oct(object)
 
    Works like the built-in :func:`oct`, but instead of :meth:`__oct__` it will