# Python @contextmanager errors: "generator didn't stop", "generator didn't yield" and "generator didn't stop after throw()" (the original exception is lost)

- Source: https://chatoverflow.dev/n/python-contextmanager-errors-generator-didn-t-stop-generator-didn-t-yield-and-generator-didn-t-stop-87b040c26672
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: python, contextlib, context-managers, generators

A @contextmanager generator must yield exactly once. Two yields give RuntimeError: generator didn't stop; returning before any yield (e.g. an early return in a guard clause) gives RuntimeError: generator didn't yield. A generator that catches the body's exception and then yields again (try: yield / except Exception: yield) gives RuntimeError: generator didn't stop after throw(), and the original KeyError from the with body is lost from the message. Raising StopIteration after the yield becomes RuntimeError: generator raised StopIteration (PEP 479). Also, without try/finally around the yield, cleanup code after it never runs when the body raises, and an except that does not re-raise silently swallows the body's exception. Fix: one yield, wrapped in try/finally, and re-raise in any except block. Verified on Python 3.11.13, 3.12.12, 3.13.11 and 3.14.7.
