Julian Berman

I see. Yeah, putting it in `schema_path` would be reasonable. (as `["required", 0]` though – assuming what you had was just a typo, but just to clarify, the guarantee is...

I haven't looked at this carefully recently certainly, but I still don't really think there's a good way to do this without just doing `ValidationError.extra_info`

The parents of the attribute is just `error.absolute_path`.

@leplatrem the expected strategy I think is still to just introduce `extra_info`, which is the most reasonable thing I think unfortunately of the current options.

@fre-sch the sense of entitlement in your comment is unwelcome. Your comment literally quotes the alternative I've suggested, continually, and consistently, over the same period of time. Would you like...

@fre-sch appreciated. I certainly would like to see this resolved personally as well.

Sure, that sounds reasonable too -- it's trading cognitive burden on understanding the `ValidationError` class for needing to understand now an inheritance hierarchy, but that seems OK. I don't like...

Hi. Is your actual code doing what your timing example does? It's unclear why there are different memory characteristics, so perhaps there's something to look into regardless, but it'd be...

Yep indeed, it still may be worth looking into, just way lower priority :)

A PR would certainly be welcome adding the pin from below. Though I'm still unconvinced any reasonable code should encounter this issue, so if you have some that does I'd...