Skip to content

Conversation

@joepvandijken
Copy link
Contributor

@joepvandijken
Copy link
Contributor Author

If anyone will verify this is an actual bug, I will also try to add a regression test for this case. Currently both versions pass all tests.

@Julian
Copy link
Member

Julian commented Jun 15, 2016

Great, thanks! This does seem likely to be correct. A test would be great.

@joepvandijken
Copy link
Contributor Author

If you have any comments on the code let me know, I'm happy to address those.

@Julian
Copy link
Member

Julian commented Jun 28, 2016

Thanks so much! I'll try to have a look in the next day or two and leave any comments.

@Julian
Copy link
Member

Julian commented Jul 30, 2016

So sorry that this slipped so long. I have a comment or two, mainly revolving around that it'd be nice to try to use "real" looking data rather than "i1" and "i2", but despite that, I think the real solution is going to be whenever I have the time to make jsonschema's test suite use hypothesis (which at the current pace is far off :().

But it's certainly good enough to merge, and I'm sorry again about the wait.

@Julian Julian merged commit b2e41f6 into python-jsonschema:master Jul 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants