Z3c-form

------------------

- The last discriminator of the 'message' IValue adapter used in the
ErrorViewSnippet is called 'content', but it was looked up as the error view
itself. It is now looked up on the form's context.

- Don't let util.getSpecification() generate an interface more than once.
This causes strange effects when used in value adapters: if two adapters
use e.g. ISchema['some_field'] as a "discriminator" for 'field', with one
adapter being more specific on a discriminator that comes later in the
discriminator list (e.g. 'form' for an ErrorViewMessage), then depending on
the order in which these two were set up, the adapter specialisation may
differ, giving unexpected results that make it look like the adapter
registry is picking the wrong adapter.

- Fix trivial test failures on Python 2.4 stemming from differences in
pprint's sorting of dicts.

- Don't invoke render() when publishing the form as a view if the HTTP status
code has been set to one in the 3xx range (e.g. a redirect or not-modified
response) - the response body will be ignored by the browser anyway.

- Handle Invalid exceptions from constraints and field validators.

- Don't create unnecessary self.items in update() method of
SelectWidget in DISPLAY_MODE. Now items is a property.

- Add hidden widget templates for radio buttons and checkboxes.

------------------

- Reverted changes made in the previous release as the ``getContent``
method can return anything it wants to as long as a data manager can
map the fields to it. So ``context`` should be used for group
instantiation. In cases where ``context`` is not wanted, the group
can be instantiated in the ``update`` method of its parent group or
form. See also
https://mail.zope.org/pipermail/zope-dev/2010-January/039334.html

(So version 2.3.2 is the same as version 2.3.0.)

------------------

- ``GroupForm`` and ``Group`` now use ``getContent`` method when
instantiating group classes instead of directly accessing
``self.context``.

------------------

Refactoring
~~~~~~~~~~~

- Removed deprecated zpkg slug and ZCML slugs.

- Adapted tests to `zope.schema` 3.6.0.

- Avoid to use `zope.testing.doctestunit` as it is now deprecated.

Update
~~~~~~

- Updated German translations.

------------------

- Feature: Add ``z3c.form.error.ComputedErrorViewMessage`` factory for easy
creation of dynamically computed error messages.

- Bug: <div class="error"> was generated twice for MultiWidget and
ObjectWidget in input mode.

- Bug: Replace dots with hyphens when generating form id from its name.

- Refactored OutputChecker to its own module to allow using
``z3c.form.testing`` without needing to depend on ``lxml``.

- Refactored: Folded duplicate code in
``z3c.form.datamanager.AttributeField`` into a single property.

------------------

- Feature: The `DictionaryFieldManager` now allows all mappings
(``zope.interface.common.mapping.IMapping``), even
``persistent.mapping.PersistentMapping`` and
``persistent.dict.PersistentDict``. By default, however, the field
manager is only registered for dict, because it would otherwise get
picked up in undesired scenarios.

- Bug: Updated code to pass all tests on the latest package versions.

- Bug: Completed the Zope 3.4 backwards-compatibility. Also created a buidlout
configuration file to test the Zope 3.4 compatibility. Note: You *must* use
the 'latest' or 'zope34' extra now to get all required
packages. Alternatively, you can specify the packages listed in either of
those extras explicitely in your product's required packages.