Releases: python-jsonschema/jsonschema
Releases · python-jsonschema/jsonschema
v4.2.0
What's Changed
- Add release note about dropping support for Py 3.6 by @sir-sigurd in #869
- Load schemas via importlib.resources by @sevein in #873
- Ensure all elements of arrays are verified for uniqueness by @DrGFreeman in #875
New Contributors
- @sevein made their first contribution in #873
- @DrGFreeman made their first contribution in #875
Full Changelog: v4.1.2...v4.2.0
v4.1.2
What's Changed
- validators: Fix dependentSchemas when instance is not an object by @robherring in #850
Full Changelog: v4.1.1...v4.1.2
v4.1.1
v4.1.0
Full Changelog: v4.0.1...v4.1.0
v4.1.0a1
Full Changelog: v4.0.1...v4.1.0a1
v4.0.1
- Partial support for Draft 2020-12 (as well as 2019-09).
 Thanks to Thomas Schmidt and Harald Nezbeda.
- Falseand- 0are now properly considered non-equal even
 recursively within a container (#686). As part of this change,
 - uniqueItemsvalidation may be slower in some cases. Please feel
 free to report any significant performance regressions, though in
 some cases they may be difficult to address given the specification
 requirement.
- The CLI has been improved, and in particular now supports a --output
 option (withplain(default) orprettyarguments) to control the
 output format. Future work may add additional machine-parsable output
 formats.
- Code surrounding DEFAULT_TYPESand the legacy mechanism for
 specifying types to validators have been removed, as per the deprecation
 policy. Validators should use theTypeCheckerobject to customize
 the set of Python types corresponding to JSON Schema types.
- Validation errors now have a json_pathattribute, describing their
 location in JSON path format
- Support for the IP address and domain name formats has been improved
- Support for Python 2 has been dropped, with python_requiresproperly
 set.
- multipleOfcould overflow when given sufficiently large numbers. Now,
 when an overflow occurs,- jsonschemawill fall back to using fraction
 division (#746).
- jsonschema.__version__,- jsonschema.validators.validators,
 - jsonschema.validators.meta_schemasand
 - jsonschema.RefResolver.in_scopehave been deprecated, as has
 passing a second-argument schema to- Validator.iter_errorsand
 - Validator.is_valid.
This patch release fixes an issue with the way python_requires was declared (i.e. with how the supported Python versions were declared).
v4.0.0
- Partial support for Draft 2020-12 (as well as 2019-09).
 Thanks to Thomas Schmidt and Harald Nezbeda.
- Falseand- 0are now properly considered non-equal even
 recursively within a container (#686). As part of this change,
 - uniqueItemsvalidation may be slower in some cases. Please feel
 free to report any significant performance regressions, though in
 some cases they may be difficult to address given the specification
 requirement.
- The CLI has been improved, and in particular now supports a --output
 option (withplain(default) orprettyarguments) to control the
 output format. Future work may add additional machine-parsable output
 formats.
- Code surrounding DEFAULT_TYPESand the legacy mechanism for
 specifying types to validators have been removed, as per the deprecation
 policy. Validators should use theTypeCheckerobject to customize
 the set of Python types corresponding to JSON Schema types.
- Validation errors now have a json_pathattribute, describing their
 location in JSON path format
- Support for the IP address and domain name formats has been improved
- Support for Python 2 has been dropped, with python_requiresproperly
 set.
- multipleOfcould overflow when given sufficiently large numbers. Now,
 when an overflow occurs,- jsonschemawill fall back to using fraction
 division (#746).
- jsonschema.__version__,- jsonschema.validators.validators,
 - jsonschema.validators.meta_schemasand
 - jsonschema.RefResolver.in_scopehave been deprecated, as has
 passing a second-argument schema to- Validator.iter_errorsand
 - Validator.is_valid.