type is still ``None``, however its meaning has changed. An encoding of ``None`` now means that no special encoding and decoding of Unicode values is done by the String type. This differs from the previous behavior, where ``None`` implied that the encoding was ``utf-8``. Pass the encoding as ``utf-8`` specifically to get the older behavior back.
colander.Invalid exception to the narrative docs. - Add (existing, but previously non-API) colander.Invalid attributes to its interface within the API documentation. - Fix Chrome pre renderings.
This is a boolean representing whether an empty string is a valid value during deserialization, defaulting to ``False``.
is created with more than one member.