gh-85757: Change wording from nested to inner (GH-91811)
https://github.com/python/cpython/commit/efb87b1090a21e1be8f5f4928349eb742fd... commit: efb87b1090a21e1be8f5f4928349eb742fd17f4c branch: main author: slateny <46876382+slateny@users.noreply.github.com> committer: miss-islington <31488909+miss-islington@users.noreply.github.com> date: 2022-04-30T15:12:33-07:00 summary: gh-85757: Change wording from nested to inner (GH-91811) #85757 https://docs.python.org/3/tutorial/datastructures.html#nested-list-comprehen... I do think this is clearer, but I wonder if 'nested' should be kept though to get the terminology out there more often. So perhaps it could be something like 'inner (nested) listcomp' or 'nested (inner) listcomp' despite sounding a bit redundant Automerge-Triggered-By: GH:rhettinger files: M Doc/tutorial/datastructures.rst diff --git a/Doc/tutorial/datastructures.rst b/Doc/tutorial/datastructures.rst index 927a6722ca251..f847ee325e0d7 100644 --- a/Doc/tutorial/datastructures.rst +++ b/Doc/tutorial/datastructures.rst @@ -303,7 +303,7 @@ The following list comprehension will transpose rows and columns:: >>> [[row[i] for row in matrix] for i in range(4)] [[1, 5, 9], [2, 6, 10], [3, 7, 11], [4, 8, 12]] -As we saw in the previous section, the nested listcomp is evaluated in +As we saw in the previous section, the inner list comprehension is evaluated in the context of the :keyword:`for` that follows it, so this example is equivalent to::
participants (1)
-
miss-islington