Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatible with jsonschema 4.10.0 #46

Closed
Wim-De-Clercq opened this issue Aug 17, 2022 · 3 comments · Fixed by #47
Closed

Incompatible with jsonschema 4.10.0 #46

Wim-De-Clercq opened this issue Aug 17, 2022 · 3 comments · Fixed by #47

Comments

@Wim-De-Clercq
Copy link

Wim-De-Clercq commented Aug 17, 2022

https://pypi.org/project/jsonschema/#history

They have created their own evolve method instead of using the attrs.evolve and that breaks a lot.
https://github.com/python-jsonschema/jsonschema/blob/ae0feea5e5e8c1a80efb1f17a20b15295355518a/jsonschema/validators.py#L204-L216

I have also created an issue on their end: python-jsonschema/jsonschema#982

@p1c2u
Copy link
Collaborator

p1c2u commented Aug 25, 2022

OAS31 will be fixed but for OAS30 check the issue #48

@Wim-De-Clercq
Copy link
Author

I believe since 4.10.2 it works again even for OAS30, due to changes on jsonschema's end (python-jsonschema/jsonschema@a8c3b14).
But, as you said, it is still a technically unsupported thing.

@p1c2u p1c2u closed this as completed in #47 Aug 25, 2022
@p1c2u
Copy link
Collaborator

p1c2u commented Aug 25, 2022

thanks for your work on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants