diff options
| author | slateny <46876382+slateny@users.noreply.github.com> | 2022-04-30 22:12:33 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-04-30 22:12:33 (GMT) |
| commit | efb87b1090a21e1be8f5f4928349eb742fd17f4c (patch) | |
| tree | d52934b92d90285a4766744f5c8ead3aa120347b /Doc/tutorial/inputoutput.rst | |
| parent | 2b97d7f6dfb025c6ab8b522c26f07c621707731c (diff) | |
| download | cpython-efb87b1090a21e1be8f5f4928349eb742fd17f4c.zip cpython-efb87b1090a21e1be8f5f4928349eb742fd17f4c.tar.gz cpython-efb87b1090a21e1be8f5f4928349eb742fd17f4c.tar.bz2 | |
gh-85757: Change wording from nested to inner (GH-91811)
#85757
https://docs.python.org/3/tutorial/datastructures.html#nested-list-comprehensions
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
Diffstat (limited to 'Doc/tutorial/inputoutput.rst')
0 files changed, 0 insertions, 0 deletions