diff options
author | Julian Berman <Julian@GrayVines.com> | 2019-02-25 19:24:18 -0500 |
---|---|---|
committer | Julian Berman <Julian@GrayVines.com> | 2019-02-25 19:24:18 -0500 |
commit | 2e082b58e44356a4acd7832f46cbf91423373380 (patch) | |
tree | 13ff2cdec065eb809b3155583278bf5114a159ef /jsonschema | |
parent | 45e2c0cec7d305b51fbec65363d94c66e7320141 (diff) | |
download | jsonschema-2e082b58e44356a4acd7832f46cbf91423373380.tar.gz |
Hopefully clarify that this function is really only the most simple entry.
Diffstat (limited to 'jsonschema')
-rw-r--r-- | jsonschema/validators.py | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/jsonschema/validators.py b/jsonschema/validators.py index 255daff..a49e125 100644 --- a/jsonschema/validators.py +++ b/jsonschema/validators.py @@ -843,10 +843,12 @@ def validate(instance, schema, cls=None, *args, **kwargs): :func:`validate` will first verify that the provided schema is itself valid, since not doing so can lead to less obvious error messages and fail - in less obvious or consistent ways. If you know you have a valid schema - already or don't care, you might prefer using the - `IValidator.validate` method directly on a specific validator - (e.g. ``Draft7Validator.validate``). + in less obvious or consistent ways. + + If you know you have a valid schema already, especially if you + intend to validate multiple instances with the same schema, you + likely would prefer using the `IValidator.validate` method directly + on a specific validator (e.g. ``Draft7Validator.validate``). Arguments: |