Julian Berman

It is, yes, but I don't want 2 (which undoubtedly eventually becomes 3 and 4 and ..) when a decently designed interface solves both issues and seems likely to solve...

And by the way, requests' json method cannot just be replaced with json.loads unfortunately, which is almost the whole reason we use requests. It implements what the json spec says...

Yep definitely makes sense on PR to propose something! On Wed, Oct 24, 2018, 09:44 marmeladema wrote: > It is, yes, but I don't want 2 (which undoubtedly eventually becomes...

> (Also, if there's a reason not use do this, I'd like to know) > This seems to work fine, although if the API settles down, I would just inherit...

A new bug with a minimal reproducer would definitely help. I don't know that we can promise any order to `Validator.iter_errors`, but if there's a simple way the library messes...

This is too difficult given how much differentiation exists between specification version documents upstream. If any effort for this ever happens it'll be in a separate repo.

(Will come back to this in more detail) Thanks for filing -- yeah, I was somewhat aware of this at the time. Really the only way to do this "well"...

I'd need some sort of reproducer -- there are plenty of tests for validate, so it's certainly not failing in all cases. What schema and instance are you validating either...

Thanks, it'd also be helpful if you minimized that to the smallest hanging example.

What I mean is it's helpful to me or anyone who can spare time to debug if you provide a [minimal working example of the issue](https://en.m.wikipedia.org/wiki/Minimal_reproducible_example) rather than one with...