Bump jsonschema from 3.2.0 to 4.0.1

[dependabot]

Bumps jsonschema from 3.2.0 to 4.0.1.

Release notes

Sourced from jsonschema's releases.

v4.0.1

• Partial support for Draft 2020-12 (as well as 2019-09). Thanks to Thomas Schmidt and Harald Nezbeda.
• False and 0 are now properly considered non-equal even recursively within a container (#686). As part of this change, uniqueItems validation 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 (with plain (default) or pretty arguments) to control the output format. Future work may add additional machine-parsable output formats.
• Code surrounding DEFAULT_TYPES and the legacy mechanism for specifying types to validators have been removed, as per the deprecation policy. Validators should use the TypeChecker object to customize the set of Python types corresponding to JSON Schema types.
• Validation errors now have a json_path attribute, 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_requires properly set.
• multipleOf could overflow when given sufficiently large numbers. Now, when an overflow occurs, jsonschema will fall back to using fraction division (#746).
• jsonschema.__version__, jsonschema.validators.validators, jsonschema.validators.meta_schemas and jsonschema.RefResolver.in_scope have been deprecated, as has passing a second-argument schema to Validator.iter_errors and 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.
• False and 0 are now properly considered non-equal even recursively within a container (#686). As part of this change, uniqueItems validation 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 (with plain (default) or pretty arguments) to control the output format. Future work may add additional machine-parsable output formats.
• Code surrounding DEFAULT_TYPES and the legacy mechanism for specifying types to validators have been removed, as per the deprecation policy. Validators should use the TypeChecker object to customize the set of Python types corresponding to JSON Schema types.

... (truncated)

Changelog

Sourced from jsonschema's changelog.

v4.0.0

• Partial support for Draft 2020-12 (as well as 2019-09). Thanks to Thomas Schmidt and Harald Nezbeda.
• False and 0 are now properly considered non-equal even recursively within a container (#686). As part of this change, uniqueItems validation 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 (with plain (default) or pretty arguments) to control the output format. Future work may add additional machine-parsable output formats.
• Code surrounding DEFAULT_TYPES and the legacy mechanism for specifying types to validators have been removed, as per the deprecation policy. Validators should use the TypeChecker object to customize the set of Python types corresponding to JSON Schema types.
• Validation errors now have a json_path attribute, 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_requires properly set.
• multipleOf could overflow when given sufficiently large numbers. Now, when an overflow occurs, jsonschema will fall back to using fraction division (#746).
• jsonschema.__version__, jsonschema.validators.validators, jsonschema.validators.meta_schemas and jsonschema.RefResolver.in_scope have been deprecated, as has passing a second-argument schema to Validator.iter_errors and Validator.is_valid.

Commits

• e61dcbc Merge pull request #846 from tirkarthi/fix-python-requires
• a7f55e2 Move python_requires to options for correct METADATA generation.
• 4f4012c Add the Zenodo badge.
• 86e41f3 Style
• 38b4c60 Remove the added argument to jsonschema.validators.create. ...
• 1790fcc Make it clear that support for draft2020-12 is partial unfortunately.
• f91f3ec Merge pull request #841 from hugovk/rm-universal
• 3da1fcf Ignore build files
• 97057ed No need to build universal wheels for Python 3-only
• dbda4f7 Merge pull request #834 from Julian/pre-commit-ci-update-config
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)