ChainMap.new_child could IMO be improved through allowing an optional dict to be passed, which is used to create the child. The use case is that you sometimes need to temporarily push a new non-empty mapping in front of an existing chain. This could be achieved by changing new_child to the following, which is backwards-compatible:

    def new_child(self, d=None):
        'New ChainMap with a new dict followed by all previous maps.'
        return self.__class__(d or {}, *self.maps)

I agree that this would be useful.

I'd like to have this feature too. However the code should use

   d if d is not None else {}

instead of

   d or {}

For example I might want to use a subclass of dict (lowerdict) that converts all keys to lowercase. When I use an empty lowerdict in new_child(), new_child() would silently use a normal dict instead:

   class lowerdict(dict):
       def __getitem__(self, key):
           return dict.__getitem__(
               self,
               key.lower() if isinstance(key, str) else key
           )
   
   import collections
   
   cm = collections.ChainMap(lowerdict(), lowerdict())
   
   cm2 = cm.new_child(lowerdict())
   
   print(type(cm2.maps[0]))

This would print <class 'dict'>.

> d if d is not None else {}

Your intention makes sense, though I would prefer to write it as:

    if d is None:
        d = {}
    return self.__class__(d, *self.maps)

Can you write-up a patch with tests and a doc change?

> Can you write-up a patch with tests and a doc change?

Done.

Put a *versionchanged* tag in the doc entry and this is ready to apply.

Also, please change the variable name from *amap* to either *m* or *mapping*.

New changeset c0ddae67f4df by Vinay Sajip in branch 'default':
Closes #16613: Added optional mapping argument to ChainMap.new_child.
http://hg.python.org/cpython/rev/c0ddae67f4df