summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorR David Murray <rdmurray@bitdance.com>2014-09-29 14:19:20 (GMT)
committerR David Murray <rdmurray@bitdance.com>2014-09-29 14:19:20 (GMT)
commitd034ece5b3150be8ba5d48d79b45379ec767cfa3 (patch)
tree3af22c7706815f6560a27fd322d5a5ffcfd8fdee
parent6c7a4182f59ab839945b6bb88aca85df07815f6d (diff)
parent12dc0d96e0b32f3ee0aeba2e93994ff5e11bec29 (diff)
downloadcpython-d034ece5b3150be8ba5d48d79b45379ec767cfa3.zip
cpython-d034ece5b3150be8ba5d48d79b45379ec767cfa3.tar.gz
cpython-d034ece5b3150be8ba5d48d79b45379ec767cfa3.tar.bz2
Merge: #20135: FAQ entry for list mutation. (See also 90b07d422bd9.)
I accidentally merged this in 90b07d422bd9; this merge addresses the last review comments on the patch.
-rw-r--r--Doc/faq/programming.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/faq/programming.rst b/Doc/faq/programming.rst
index abadc95..ffb7e8b 100644
--- a/Doc/faq/programming.rst
+++ b/Doc/faq/programming.rst
@@ -473,7 +473,7 @@ There are two factors that produce this result:
After the call to :meth:`~list.append`, the content of the mutable object has
changed from ``[]`` to ``[10]``. Since both the variables refer to the same
-object, accessing either one of them accesses the modified value ``[10]``.
+object, using either name accesses the modified value ``[10]``.
If we instead assign an immutable object to ``x``::