Nti.schema

==================

- Add ``VariantValidationError``, an error raised by variant fields
when none of their constituent fields could adapt or validate the
value.

==================

- Add support for ``IFromBytes`` in zope.schema 4.8.0.

- The ``Variant`` and ``ListOrTupleFromObject``, ``TupleFromObject``,
``DictFromObject`` fields all have tweaked behaviour in
``fromObject``. If the incoming value is a bytestring or text
string, the underlying field's ``fromBytes`` and ``fromUnicode``
will be called in preference to a ``fromObject``, if that method is
implemented.

- ``ValidSet`` and ``UniqueIterable`` now implement ``fromObject``.

- All fields that implement ``fromObject`` now accept an ``Object``
field for their ``value_type`` (and ``key_type`` in the case of
``DictFromObject``) and will attempt to adapt objects that do not
provide the schema in ``fromObject``.

==================

- Adjust the deprecated ``zope.schema.interfaces.InvalidValue`` to be
a simple alias for ``zope.schema.interfaces.InvalidValue`` (while
preserving the constructor) for improved backwards compatibility.

==================

- Add support for zope.schema 4.7.0; drop support for older versions.

==================

- Fix the ``repr`` of ``nti.schema.interfaces.InvalidValue``. See
`issue 26 <https://github.com/NextThought/nti.schema/issues/26>`_.

- ``nti.schema.jsonschema`` turns more abstract field types into
concrete types. See `issue 29 <https://github.com/NextThought/nti.schema/issues/29>`_.

==================

- Make ``nti.schema.interfaces.InvalidValue`` a class again. It is
deprecated. See `issue 24 <https://github.com/NextThought/nti.schema/issues/24>`_.