[issue22305] Documentation on deepcopy's problems is misleading

Changes by Georg Brandl : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue22305] Documentation on deepcopy's problems is misleading

Shailesh Hegde added the comment: Thanks. "Because deep copy copies everything it may copy too much, e.g., administrative data structures that need to be shared even between copies, which may not be the desired goal." helps me understand better. -- __

[issue22305] Documentation on deepcopy's problems is misleading

Steven D'Aprano added the comment: > It should read: > "administrative data structures that should be not shared > even between copies" No. If they should NOT be shared, then making a deep copy is the correct thing to do. The problem with deepcopy is when you actually do want to share some de

[issue22305] Documentation on deepcopy's problems is misleading

New submission from Shailesh Hegde: https://docs.python.org//library/copy.html "Two problems often exist with deep copy operations that don’t exist with shallow copy operations: Recursive objects (compound objects that, directly or indirectly, contain a reference to themselves) may cause a re