whatsnew: ChainMap.new_child *m* argument.

And NEWS entry.

diff --git a/Doc/whatsnew/3.4.rst b/Doc/whatsnew/3.4.rst
index f41a6ac68a091de92bea262965051212ffa65eb6..e7fd3a9d308cbe5f3339eba0764fbc1907131f68 100644 (file)
--- a/Doc/whatsnew/3.4.rst
+++ b/Doc/whatsnew/3.4.rst
@@ -596,6 +596,15 @@ including the Adobe variant.  (Contributed by Martin Morrison, the Mercurial
 project, Serhiy Storchaka, and Antoine Pitrou in :issue:`17618`.)
 
 
+collections
+-----------
+
+The :meth:`.ChainMap.new_child` method now accepts an *m* argument specifying
+the child map to add to the chain.  This allows an existing mapping and/or a
+custom mapping type to be used for the child.  (Contributed by Vinay Sajip in
+:issue:`16613`.)
+
+
 colorsys
 --------
 

diff --git a/Misc/NEWS b/Misc/NEWS
index 68cb3790abbe3d15fd69aeaef1ab1a293a9c1c72..214e8fc34db7a2d93d0f2f7c0bf72723b357ec94 100644 (file)
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -2376,6 +2376,9 @@ Core and Builtins
 - Issue #14850: Now a charmap decoder treats U+FFFE as "undefined mapping"
   in any mapping, not only in a string.
 
+- Issue #16613: Add *m* argument to ``collections.Chainmap.new_child`` to
+  allow the new child map to be specified explicitly.
+
 - Issue #16730: importlib.machinery.FileFinder now no longers raises an
   exception when trying to populate its cache and it finds out the directory is
   unreadable or has turned into a file. Reported and diagnosed by