Skip to content

Clarify docs on checkpoints in async iterables #2390

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
Zac-HD merged 1 commit into from
Aug 19, 2022
Merged

Clarify docs on checkpoints in async iterables #2390

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions docs/source/reference-core.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,9 +90,9 @@ them. Here are the rules:
exception, it might act as a checkpoint or might not.)

* This includes async iterators: If you write ``async for ... in <a
trio object>``, then there will be at least one checkpoint before
each iteration of the loop and one checkpoint after the last
iteration.
trio object>``, then there will be at least one checkpoint in
each iteration of the loop, and it will still checkpoint if the
iterable is empty.

* Partial exception for async context managers:
Both the entry and exit of an ``async with`` block are
Expand Down