[issue36060] Document how collections.ChainMap() determines iteration order

Raymond Hettinger added the comment: New changeset 86f093f71a594dcaf21b67ba13dda72863e9bde9 by Raymond Hettinger in branch 'master': bpo-36060: Document how collections.ChainMap() determines iteration order (GH-11969)

[issue36060] Document how collections.ChainMap() determines iteration order

Change by miss-islington : -- pull_requests: +12002 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36060] Document how collections.ChainMap() determines iteration order

Raymond Hettinger added the comment: New changeset 7121a6eeb7941f36fb9e7eae28ec24ecfa533e81 by Raymond Hettinger (Miss Islington (bot)) in branch '3.7': bpo-36060: Document how collections.ChainMap() determines iteration order (GH-11969) (GH-11978)

[issue36060] Document how collections.ChainMap() determines iteration order

Change by Raymond Hettinger : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue36060] Document how collections.ChainMap() determines iteration order

Change by Raymond Hettinger : -- keywords: +patch pull_requests: +11995 stage: -> patch review ___ Python tracker ___ ___

[issue36060] Document how collections.ChainMap() determines iteration order

New submission from Raymond Hettinger : Am working on a PR for this now. Prior to regular dicts becoming ordered, the was no expectation for ChainMap() to have any particular order. Now that such an expectation might exist, I need to document what ChainMap() does and perhaps why it does it.