gh-141984: Add "exhausted" to glossary, link existing mentions - #157225
Conversation
Co-authored-by: Blaise Pabon <blaise@gmail.com>
Documentation build overview
|
Co-authored-by: Stan Ulbrych <stan@python.org>
|
Thanks @encukou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
|
Thanks @encukou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
|
Thanks @encukou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.15. |
|
Sorry, @encukou, I could not cleanly backport this to |
|
Sorry, @encukou, I could not cleanly backport this to |
|
Sorry, @encukou, I could not cleanly backport this to |
|
GH-157271 is a backport of this pull request to the 3.15 branch. |
|
GH-157272 is a backport of this pull request to the 3.14 branch. |
…GH-157225) (GH-157272) (cherry picked from commit 9bd670c) Co-authored-by: Petr Viktorin <encukou@gmail.com> Co-authored-by: Blaise Pabon <blaise@gmail.com>
…GH-157225) (#157271) Co-authored-by: Blaise Pabon <blaise@gmail.com> Co-authored-by: Stan Ulbrych <stan@python.org>
The term “exhausted” is used quite a lot for iterators. Add a glossary entry for it, and link to that from all relevant uses. (Things like memory exhaustion or non-exhaustive lists aren't linked.)
(Tagged with #141984 since this grew out of improving syntax docs. It's only tangentially related, but IMO better than not linking to an issue.)