# PEP 678: Enriching Exceptions with Notes

**URL:** https://discuss.python.org/t/pep-678-enriching-exceptions-with-notes/13374
**Category:** PEPs
**Created:** [January 27, 2022, 9:29am UTC](https://discuss.python.org/t/pep-678-enriching-exceptions-with-notes/13374 "2022-01-27T09:29:53Z")
**Posts on this page:** 1
**Showing post:** 98

<div class="post-metadata">

### Author: ![Conchylicultor](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/conchylicultor/32/4052_2.png) [@Conchylicultor](https://discuss.python.org/u/Conchylicultor)
#### Post date: [March 31, 2022, 2:52pm UTC](https://discuss.python.org/t/pep-678-enriching-exceptions-with-notes/13374/98 "2022-03-31T14:52:36Z")

</div>

> [@iritkatriel](#):
>
> We are not suggesting to mutate the `traceback` , but to use the building blocks in `traceback` to control how an exception is rendered (at the time of rendering, not at library import time).

I apologize if I haven’t understood what you suggested. Could you give an example ?

How can I update the exception in-place to modify the way it will be rendered when:

- I don’t control the original exception (can be any custom user exception)
- I don’t control the user code in which the exception is propagated

---

_[View the full topic](https://discuss.python.org/t/pep-678-enriching-exceptions-with-notes/13374)._