summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSanyam Khurana <CuriousLearner@users.noreply.github.com>2017-04-09 10:22:30 (GMT)
committerNick Coghlan <ncoghlan@gmail.com>2017-04-09 10:22:30 (GMT)
commit19e04942562a980ad2519f6ff79c455a7472783b (patch)
tree808c001f003bb17828e04e35f40d4715beb6352b
parent0e6cb2ea624570ed08c354f1ed1f595dab4192d6 (diff)
downloadcpython-19e04942562a980ad2519f6ff79c455a7472783b.zip
cpython-19e04942562a980ad2519f6ff79c455a7472783b.tar.gz
cpython-19e04942562a980ad2519f6ff79c455a7472783b.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.
-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 70678c3..962a3c7 100644
--- a/Misc/ACKS
+++ b/Misc/ACKS
@@ -773,6 +773,7 @@ Lawrence Kesteloot
Vivek Khera
Dhiru Kholia
Akshit Khurana
+Sanyam Khurana
Mads Kiilerich
Jason Killen
Jan Kim