A 'value attribute for ValueError could store a weakref to the value which triggered the exception. It should be a weakref so at to prevent accidental prevention of GC of the value.

Just a gentle reminder guys.

There's actually no advantage for a weakref here, since the exception object already holds an indirect reference to all the raising frame's locals through __traceback__.

So, this is actually impossible to do.
Since exceptions are c-level classes, adding members to ValueError means anything that multiple-inherits from ValueError and any other complex exception gets a multiple bases layout conflict. There's already one such class - _pyio.UnsupportedOperation inherits both ValueError and OSError - but the bigger issue is that this would break compatibility.

After discussing it (face-to-face) with a bunch of core devs, I think the only reasonable course of action is to close the issue and never speak of this again.

Thanks for the analysis. Closing then!

nosy: + pitrou
messages: + msg241042

resolution: rejected
stage: test needed -> resolved

messages: + msg228594
versions: + Python 3.5, - Python 3.4