Skip to content

gh-135171: Update documentation for the generator expression #135351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gpshead merged 2 commits into from
Jun 15, 2025
Merged

gh-135171: Update documentation for the generator expression #135351

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
274bfee
gh-135171: Update documentation for the generator expression
serhiy-storchaka Jun 10, 2025
34d791f
Update Doc/reference/expressions.rst
serhiy-storchaka Jun 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update Doc/reference/expressions.rst 
Co-authored-by: Brian Skinn <brian.skinn@gmail.com>
  • Loading branch information
@serhiy-storchaka @bskinn
serhiy-storchaka and bskinn authored Jun 10, 2025
commit 34d791faf1ea9a3dde45196d1c381952f065d73d
2 changes: 1 addition & 1 deletion Doc/reference/expressions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -408,7 +408,7 @@ Variables used in the generator expression are evaluated lazily when the
fashion as normal generators). However, the iterable expression in the
leftmost :keyword:`!for` clause is immediately evaluated, and the
Comment thread
gpshead marked this conversation as resolved.
:term:`iterator` is immediately created for that iterable, so that an error
produced by it will be emitted at the point where the generator expression
produced while creating the iterator will be emitted at the point where the generator expression
is defined, rather than at the point where the first value is retrieved.
Subsequent :keyword:`!for` clauses and any filter condition in the leftmost
Comment thread
serhiy-storchaka marked this conversation as resolved.
:keyword:`!for` clause cannot be evaluated in the enclosing scope as they may
Expand Down