Skip to content

Conversation

@slateny
Copy link
Contributor

@slateny slateny commented Apr 22, 2022

#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

@bedevere-bot bedevere-bot added docs Documentation in the Doc dir awaiting review labels Apr 22, 2022
@peendebak
Copy link
Contributor

Inner seems a better choice than nested. To keep terms consistent, also change nested to inner on line 321:

# the following 3 lines implement the nested listcomp

@slateny

@slateny
Copy link
Contributor Author

slateny commented Apr 27, 2022

For a tutorial, wouldn't it be a good idea to sprinkle in terminology like 'nested' here and there? I do think using inner is clearer in this case but I wonder if keeping some cases of neated would be good so the reader gets used to seeing them

@peendebak
Copy link
Contributor

For a tutorial, wouldn't it be a good idea to sprinkle in terminology like 'nested' here and there? I do think using inner is clearer in this case but I wonder if keeping some cases of neated would be good so the reader gets used to seeing them

I don't have a strong opinion here. Both inner and nested are ok to use

Co-authored-by: Pieter Eendebak <P.T.eendebak@tudelft.nl>
@miss-islington
Copy link
Contributor

@slateny: Status check is done, and it's a success ✅ .

@miss-islington miss-islington merged commit efb87b1 into python:main Apr 30, 2022
@slateny slateny deleted the s/tutorial-nested branch May 4, 2022 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation in the Doc dir skip news

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants