Brett Cannon added the comment:

A potential compromise would be if ValueError gained a 'value' attribute. That 
would allow for the exception message to be static but still provide the 
information for introspection later if desired to figure out exactly what 
object led to the cause of the ValueError. If I remember correctly previous 
objections to this idea was worry about memory, though, so it seems attaching 
more information about the trigger of a ValueError will inevitably lead to more 
cost somehow.


Python tracker <>
Python-bugs-list mailing list

Reply via email to