| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
|
|
||
| The :keyword:`for` statement is used to iterate over the elements of a sequence | ||
| (such as a string, tuple or list) or other iterable object: | ||
| (such as a string, tuple, or list) or other iterable object: |
There was a problem hiding this comment.
Please see warnings on your pr.
Sorry, something went wrong.
There was a problem hiding this comment.
okay yea saw it. found a "starred_expression_list" in the https://docs.python.org/3/reference/expressions.html#grammar-token-python-grammar-starred_expression_list. I will try to link it to that instead then
Sorry, something went wrong.
There was a problem hiding this comment.
@skirpichev done, i reviewed it locally and doc seems proper. starred_list is turned into starred_expression_list mentioned already in https://docs.python.org/3/reference/expressions.html#grammar-token-python-grammar-starred_expression_list
Sorry, something went wrong.
There was a problem hiding this comment.
Why this comma? Seems unrelated to the pr content.
Sorry, something went wrong.
There was a problem hiding this comment.
Why this comma? Seems unrelated to the pr content.
While changing i just noticed a small grammar error and thought of fixing it. Its a small mistake but comma should be there after the tuple, I can make a separate PR for it if you want
Sorry, something went wrong.
There was a problem hiding this comment.
@StanFromIreland, does this looks correct for you?
Sorry, something went wrong.
There was a problem hiding this comment.
It is an oxford comma, its usage is varied across contexts, but generally recommended in formal writing.
It is unrelated to this pr and not very important, I am not against it staying, but I wouldn't be heavily opposed to removing it either.
Sorry, something went wrong.
|
@skirpichev do i need to fix something? i dont know what being marked as draft is suppose to imply |
Sorry, something went wrong.
There was a problem hiding this comment.
You can mark it as ready for review whenever you feel it is. Currently it is not.
See my comments, and I recommended you read the devguide. (Sections on documentation and pr lifecycle will be particularly handy now)
Sorry, something went wrong.
…stmt-docs # Conflicts: # Doc/reference/compound_stmts.rst
There was a problem hiding this comment.
Minor change needed otherwise good to go
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, but please fix long lines.
Sorry, something went wrong.
| The first item provided | ||
| by the iterator is then assigned to the target list using the standard | ||
| The :token:`~python-grammar:starred_expression_list` expression is evaluated once; | ||
| it should yield an :term:`iterable` object. An :term:`iterator` is created for that iterable. |
There was a problem hiding this comment.
If you change this line in any case, please break it between sentences. Otherwise the line is too long. Even if the linter is silent, the recommended size is less than 80 columns.
Sorry, something went wrong.
|
Thanks @Yash-Vijay29 for the PR, and @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Sorry, something went wrong.
|
Thank you for the fix! |
Sorry, something went wrong.
|
GH-134424 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
What’s changed
Why
Backwards compatibility
Further notes
📚 Documentation preview 📚: https://cpython-previews--134034.org.readthedocs.build/