[issue23802] patch: __deepcopy__ memo dict argument usage

Change by Joannah Nanjekye : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list m

[issue23802] patch: __deepcopy__ memo dict argument usage

Irit Katriel added the comment: This seems resolved, can it be closed? -- nosy: +iritkatriel ___ Python tracker ___ ___ Python-bugs

[issue23802] patch: __deepcopy__ memo dict argument usage

Joannah Nanjekye added the comment: New changeset 3cbade7d309ab1ea97ec286d19d506df30bd1ab7 by Joannah Nanjekye in branch 'master': bpo-23802: patch: __deepcopy__ memo dict argument usage (GH-21326) https://github.com/python/cpython/commit/3cbade7d309ab1ea97ec286d19d506df30bd1ab7 --

[issue23802] patch: __deepcopy__ memo dict argument usage

Joannah Nanjekye added the comment: The Pr should sort this. I will merge it tommorrow if there is no objection. -- ___ Python tracker ___

[issue23802] patch: __deepcopy__ memo dict argument usage

Change by Joannah Nanjekye : -- nosy: +nanjekyejoannah nosy_count: 3.0 -> 4.0 pull_requests: +20476 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21326 ___ Python tracker __

[issue23802] patch: __deepcopy__ memo dict argument usage

R. David Murray added the comment: I would rather say simply "The memo dictionary should be treated as an opaque object". On the other hand, I doubt we will ever change the structure of the memo dict, because I'm sure that somewhere out there there is code that is *not* treating it as opaque

[issue23802] patch: __deepcopy__ memo dict argument usage

New submission from Daniel Shahaf: In the 'copy' module documentation, it wasn't fully clear to me how __deepcopy__ implementations should treat the memo dict argument. The attached patch clarifies that __deepcopy__ implementations should treat the memo dict argument as an opaque type. -