Bug Fixes

---------

- When the ``Configurator`` is passed an instance of
  ``zope.component.registry.Components`` as a ``registry`` constructor
  argument, fix the instance up to have the attributes we expect of an
  instance of ``repoze.bfg.registry.Registry`` when ``setup_registry``
  is called.  This makes it possible to use the global Zope component
  registry as a BFG application registry.

Documentation
-------------

- Change renderings of ZCML directive documentation.

- Add a narrative documentation chapter: "Using the Zope Component
  Architecture in ``repoze.bfg``"

1 files changed, 0 insertions, 3 deletions

diff --git a/docs/zcml/static.rst b/docs/zcml/static.rst
index 23cd57538..1a11f222c 100644
--- a/docs/zcml/static.rst
+++ b/docs/zcml/static.rst
@@ -12,13 +12,11 @@ Attributes
 ~~~~~~~~~~
 
 ``name``
-
   The (application-root-relative) URL prefix of the static directory.
   For example, to serve static files from ``/static`` in most
   applications, you would provide a ``name`` of ``static``.
 
 ``path``
-
   A path to a directory on disk where the static files live.  This
   path may either be 1) absolute (e.g. ``/foo/bar/baz``) 2)
   Python-package-relative (e.g. (``packagename:foo/bar/baz``) or 3)
@@ -26,7 +24,6 @@ Attributes
   contains the directive (e.g. ``foo/bar/baz``).
 
 ``cache_max_age``
-
   The number of seconds that the static resource can be cached, as
   represented in the returned response's ``Expires`` and/or
   ``Cache-Control`` headers, when any static file is served from this