> def not_valid(instance, schema):
> try:
> return validate(instance, schema)
> except ValidationError as err:
> return str(err)
It does, I recognize that. If I had the "exception ternary" that didn't capture the exception, I'd probably just evaluate to a True instead in the exception case... then go back to revalidate manually only in the unexpected case of validity failing. Of course, if some nice looking syntax did both, so much the better. Even the simpler form would have helped me though.
I also know it is better in my example to return the exception object itself rather than just its stringification. If I were publishing my API more widely, rather than the internal use I had, I would have done that.
The dead increasingly dominate and strangle both the living and the
not-yet born. Vampiric capital and undead corporate persons abuse
the lives and control the thoughts of homo faber. Ideas, once born,
become abortifacients against new conceptions.