first cut at exposing and using 'retail' api for templating, currently requires feature.exposesub2 branch of colander, and has no additional tests
- Deform now depends on Colander >= 0.9.9dev (previously it depended on >=
  0.8).  It requires Colander 0.9.9's newer ``cstruct_children`` and
  ``appstruct_children`` methods of schema objects as well as being able to
  import objects from Colander that don't exist in earlier versions.

- Deform now depends on Chameleon >= 2.5.1 (previously it depended on
  >= 1.2.3).  It requires the Markup class supplied by this version or better.

- Deform no longer has a setup_requires dependency on setuptools_git
  (useless, as the version on PyPI is broken).

- The default widget for the colander.Money type is now
  deform.widgets.MoneyInputWidget.

- Setup.py now includes all testing requirements in tests_require that are in
  testing extras and vice versa.

- In support of "retail" form rendering, the ``serialize`` method of widgets
  now accepts arbitrary keyword arguments.  These are used as top-level value
  overrides to widget templates.

- In support of "retail" form rendering, the ``serialize`` method of a Field
  now accepts arbitrary keyword arguments.  These are passed along to it's
  widget's ``serialize`` method.

- Built-in widgets now pass more top-level names to their templates.
  Previously only two names were always passed to templates: ``field`` and
  ``cstruct``.  Those are still passed, but now many others are passed.  The
  top-level template rendering dictionary is created in the following way:

  - All non-method, non-dunder attributes of the widget (both its __dict__
    and its' class' __dict__ and any other attributes in the widget's mro)
    are scraped off the widget and turned into top-level names.  These are
    turned in to a dictionary.  One exception: ``template`` is omitted (it is
    used in method calls so it can't be a part of the dict).

  - The values ``field`` (representing the form field) and ``cstruct``
    (representing the cstruct value passed to the renderer) are added to the
    dictionary.  These replace any attributes that already exist in the
    dictionary.

  - The following attributes are scraped off the field and added to the
    dictionary: ``oid``, ``name``, ``description``, ``title``, and
    ``required``.  These replace any of the attributes that already exist in
    the dictionary.

  - An arbitrary set of key-value pairs passed to the widget's ``serialize``
    method are added to the dictionary.  These replace any values that
    already exist in the dictionary.

  The ultimate dictionary composed this way is used as the top-level
  dictionary passed to every template rendered by built-in widgets.  This
  feature is in support of "retail" form rendering.

- Built-in templates have been changed to use top-level names where feasible
  instead of attributes of ``field`` and/or ``cstruct`` so their uses may be
  overridden by a caller to ``serialize``.  This is in support of "retail"
  form rendering.

- Built-in widgets may have a 'readonly' attribute/constructor-argument, to
  indicate that a form field associated with the widget should use its
  readonly template instead of its normal readwrite template.  A ``readonly``
  keyword argument can still be passed to ``Field.serialize`` to render a
  field as readonly, like in older versions.

- It is now possible to pass an ``appstruct`` argument to the
  ``deform.Field`` (and by extension, the ``deform.Form``) constructor.  When
  you do so, you can omit passing an ``appstruct`` argument to the ``render``
  method of the field/form.  Fields set a cstruct value recursively when
  supplied with an appstruct.  This is in support of "retail" form rendering.

- Form/field objects are now initialized with a cstruct (recursively) when
  created.  This means that accessing form.cstruct will return the current
  set of rendering values.  This value is reset during validation, so after a
  validation is done you can re-render the form to show validation errors.
  This is in support of "retail" form rendering.

- Form/field objects now have peppercorn-field-outputting methods:
  ``start_mapping``, ``end_mapping``, ``start_sequence``, ``end_sequence``,
  ``start_rename``, ``end_rename``.
reverse previous decision to pass a mess-o-names into templates; get rid of dead chameleon 1 code
get rid of render_widget, it's now logically the same as serialize.  garden changelog.  fix a template name reference
slightly better coverage
Merge branch 'master' into feature.retail
coverage