summaryrefslogtreecommitdiff
path: root/Doc
diff options
context:
space:
mode:
authorR David Murray <rdmurray@bitdance.com>2014-09-29 10:17:28 -0400
committerR David Murray <rdmurray@bitdance.com>2014-09-29 10:17:28 -0400
commit12dc0d96e0b32f3ee0aeba2e93994ff5e11bec29 (patch)
treeea812b7e31423e7a0dac2e4965cf6c23b8b78ceb /Doc
parentc31f12d196455e916fcbcffc2cc2a3329abe70ed (diff)
downloadcpython-git-12dc0d96e0b32f3ee0aeba2e93994ff5e11bec29.tar.gz
#20135: FAQ entry for list mutation. (See also 6375bf34fff6.)
I accidentally committed this in 6375bf34fff6; this changeset addresses the last review comments on the patch. This is a perennial question and something someone opens a ticket for probably every other month or so, so I'm surprised we didn't already have a FAQ entry for it. The original patch was written by M. Votz, refined first by Ezio Melotti and further refined by me.
Diffstat (limited to 'Doc')
-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 abadc954b4..ffb7e8b13b 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``::