summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNick Coghlan <ncoghlan@gmail.com>2017-04-09 10:57:15 (GMT)
committerGitHub <noreply@github.com>2017-04-09 10:57:15 (GMT)
commitbd18351c31573ab9a8580677004370a774a4eaae (patch)
tree45710c6ef0c4c04aa92b3430ca7fe6c9d0baa6e4
parentc82d39479a88154bd72a3a304be5f473c118da95 (diff)
downloadcpython-bd18351c31573ab9a8580677004370a774a4eaae.zip
cpython-bd18351c31573ab9a8580677004370a774a4eaae.tar.gz
cpython-bd18351c31573ab9a8580677004370a774a4eaae.tar.bz2
bpo-29506: Clarify deep copy note in copy module
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)
-rw-r--r--Doc/library/copy.rst4
-rw-r--r--Misc/ACKS1
2 files changed, 3 insertions, 2 deletions
diff --git a/Doc/library/copy.rst b/Doc/library/copy.rst
index d0b861d..2041d91 100644
--- a/Doc/library/copy.rst
+++ b/Doc/library/copy.rst
@@ -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:
diff --git a/Misc/ACKS b/Misc/ACKS
index 4279083..babd495 100644
--- 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