Upgrade jsonschema to 4.x #205
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
@stevenday, hi and thank you! Will try to get at this shortly, appreciate the PR 🙏 |
Author
|
It looks like you've bumped the jsonschema version as part of #206 and this would be obsolete once that lands anyway, so I'll close it to keep things tidy. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
We are happy users of tilesets-cli, thank you! However, the dependency on jsonschema~=3.0 recently has caused us some problems because our data pipeline tool, prefect, depends on 4.x.
Version 4 of jsonschema was released in 2022, but happily it doesn't look like the
validatefunction you use has changed between versions.I've upgraded the version in requirements.txt and updated the pin in setup.py and it all seems to work fine for me.