summaryrefslogtreecommitdiff
path: root/docs/narr/viewconfig.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/narr/viewconfig.rst')
-rw-r--r--docs/narr/viewconfig.rst8
1 files changed, 0 insertions, 8 deletions
diff --git a/docs/narr/viewconfig.rst b/docs/narr/viewconfig.rst
index 9b2074a70..3f2b1b179 100644
--- a/docs/narr/viewconfig.rst
+++ b/docs/narr/viewconfig.rst
@@ -63,11 +63,6 @@ View configuration is performed in one of these ways:
:meth:`pyramid.config.Configurator.add_route` method, passing a ``view``
argument specifying a view callable.
-.. note:: You can also add view configuration by adding a ``<view>`` or
- ``<route>`` declaration to :term:`ZCML` used by your application as per
- :ref:`mapping_views_using_zcml_section`, :ref:`view_directive` or
- :ref:`route_directive`.
-
.. note:: A package named ``pyramid_handlers`` (available from PyPI) provides
an analogue of :term:`Pylons` -style "controllers", which are a special
kind of view class which provides more automation when your application
@@ -443,9 +438,6 @@ you *must* do use the ``scan`` method of a
# pyramid.config.Configurator class
config.scan()
-.. note:: See :ref:`zcml_scanning` for information about how to invoke a scan
- via ZCML (if you're not using imperative configuration).
-
Please see :ref:`decorations_and_code_scanning` for detailed information
about what happens when code is scanned for configuration declarations
resulting from use of decorators like :class:`pyramid.view.view_config`.