summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNick Coghlan <ncoghlan@gmail.com>2017-04-09 10:57:04 (GMT)
committerGitHub <noreply@github.com>2017-04-09 10:57:04 (GMT)
commita524d6307273e3920d410452ace89610c843f051 (patch)
treea938b79bc98bc5c5993722a96f8dc74b7a9c31f4
parent4c116cb3b3ee38cae229f7e0df0cd2045fe73c27 (diff)
downloadcpython-a524d6307273e3920d410452ace89610c843f051.zip
cpython-a524d6307273e3920d410452ace89610c843f051.tar.gz
cpython-a524d6307273e3920d410452ace89610c843f051.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 b5da02a..72070e1 100644
--- a/Misc/ACKS
+++ b/Misc/ACKS
@@ -770,6 +770,7 @@ Lawrence Kesteloot
Vivek Khera
Dhiru Kholia
Akshit Khurana
+Sanyam Khurana
Mads Kiilerich
Jason Killen
Jan Kim