]> granicus.if.org Git - python/commitdiff
bpo-29506: Clarify deep copy note in copy module
authorNick Coghlan <ncoghlan@gmail.com>
Sun, 9 Apr 2017 10:57:15 +0000 (20:57 +1000)
committerGitHub <noreply@github.com>
Sun, 9 Apr 2017 10:57:15 +0000 (20:57 +1000)
The reference to administrative data was confusing to readers,
so this simplifies the note to explain that deep copying may copy
more then you intended, such as data that you expected to be
shared between copies.
(cherry picked from commit 19e04942562a980ad2519f6ff79c455a7472783b)

Doc/library/copy.rst
Misc/ACKS

index d0b861d469bc05f982fff01ac66d8af2d66d2624..2041d9175ea5878555877a5d3a1c97645c3f642a 100644 (file)
@@ -47,8 +47,8 @@ copy operations:
 * Recursive objects (compound objects that, directly or indirectly, contain a
   reference to themselves) may cause a recursive loop.
 
-* Because deep copy copies *everything* it may copy too much, e.g.,
-  even administrative data structures that should be shared even between copies.
+* Because deep copy copies everything it may copy too much, such as data
+  which is intended to be shared between copies.
 
 The :func:`deepcopy` function avoids these problems by:
 
index 42790834da765f78458c0bb94457fc4383ad7405..babd4950da679733e12c62efe5ae4b7b869588fa 100644 (file)
--- a/Misc/ACKS
+++ b/Misc/ACKS
@@ -759,6 +759,7 @@ Lawrence Kesteloot
 Vivek Khera
 Dhiru Kholia
 Akshit Khurana
+Sanyam Khurana
 Mads Kiilerich
 Jason Killen
 Jan Kim