-
Notifications
You must be signed in to change notification settings - Fork 10
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
import ValidationError from asdf.exceptions #886
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Codecov Report
@@ Coverage Diff @@
## master #886 +/- ##
==========================================
- Coverage 96.47% 96.47% -0.01%
==========================================
Files 95 95
Lines 6293 6292 -1
==========================================
- Hits 6071 6070 -1
Misses 222 222
|
thanks a lot @braingram for carrying this over ! Does this require |
Thanks! Either 2.15.0 or 2.15.1 will work (2.15.0 has 2.15.1 is probably safer as it includes the jsonschema vendorization which means 2.15.0 might break at some point if jsonschema decides to change their excepetion classes in a way that is incompatible with the vendorized version (4.17.3). |
Changes
asdf has recently run into compatibility issues with jsonschema 4.18+. The newer versions of jsonschema dropped support for a feature required in asdf which left us with little choice but to vendorize jsonschema. This presented an opportunity to clean up some leaky bits of the asdf API including the issue that
jsonschema.ValidationError
was transparently passed to user code and libraries (like weldx) had to importValidationError
from jsonschema.asdf 2.15 introduced
ValidationError
as part of the public api available atasdf.exceptions.ValidationError
. The changes in this PR modify a few tests and docs to importValidationError
fromasdf.exceptions
(instead of jsonschema or from the top level asdf module).asdf 2.15.1 includes the vendorized jsonschema, keeps jsonschema as a dependency and attempts to use the exceptions from the installed jsonschema (to not break some downstream libraries that use asdf). We are planning to drop jsonschema as a dependency and stop using it's exceptions in asdf 3.0 (or possibly in 2.15.2 if further changes to jsonschema make it's exceptions incompatible).
Please see the What's New page in the asdf 2.15.1 docs for more information and let me know if you have any questions, comments or concerns.
Checks
CHANGELOG.md
tests/
doc/