Allow other versions of jsonschema, as long as they are compatible #20
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
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
TTMaZa
force-pushed
the
TTMaZa-allow-other-versions-if-jsonschema
branch
from
84eb828 to
d251220
Compare
Member
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem:
in lager projects other libs might require slightly other versions of jsonschema. Packamanegers (like poetry) are not able to resolve this kind of conflict of testguide_report-generator insists on exactly version 4.16.0
Proposed solution:
allow SemVer compatible versions of jsonschema as described here: https://python-poetry.org/docs/dependency-specification/#caret-requirements