# Using ExceptionGroup at Anthropic (experience report)

**URL:** <https://discuss.python.org/t/using-exceptiongroup-at-anthropic-experience-report/20888>\
**Category:** Async-SIG\
**Created:** [November 9, 2022, 7:21am UTC](https://discuss.python.org/t/using-exceptiongroup-at-anthropic-experience-report/20888 "2022-11-09T07:21:57Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Zac-HD](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/zac-hd/32/607_2.png) [@Zac-HD](https://discuss.python.org/u/Zac-HD)\
**Post date:** [November 15, 2022, 4:45am UTC](https://discuss.python.org/t/using-exceptiongroup-at-anthropic-experience-report/20888/6 "2022-11-15T04:45:09Z")

</div>

I spent the afternoon digging into this, and it looks like I was just mistaken: a _non-contextmanager_ async generator threw a `GeneratorExit` out through one of our context managers, and in addition to fixing the actual problem I added my `with unwrap_generatorexit():` hack to a context manager that didn’t actually need it. Apologies for the confusion, thanks for the prompt to investigate more fully, and post edited!

---

_[View the full topic](https://discuss.python.org/t/using-exceptiongroup-at-anthropic-experience-report/20888)._