| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
|
I have opened PR #135819 that clarifies the documentation. Kindly review. Thanks! |
Sorry, something went wrong.
|
Hi, thanks for contributing! There's already an open PR for this issue: #135152. That's already been approved, so I think this probably won't land. |
Sorry, something went wrong.
|
Closing as a duplicate then. In the future, look at the end of the issue to see if a PR already exists. TiA. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
gh-135110: Clarify that generator.close() does not externally raise GeneratorExit
Where: gh-135110 refers to the GitHub issue number being fixed.
This change addresses a documentation inconsistency where it was previously implied that generator.close() raises a GeneratorExit externally. However, this exception is raised inside the generator at the suspension point, and if not handled, it fails silently without propagating.
This change helps new users clearly understand how close() behaves when called on a generator.
Closes: gh-135110
-->
📚 Documentation preview 📚: https://cpython-previews--135819.org.readthedocs.build/