From 6871c162335ba54c0b55e88b4cb139c7cfaf1157 Mon Sep 17 00:00:00 2001 From: Casey Duncan Date: Sun, 5 Dec 2010 11:02:41 -0700 Subject: break run-on --- docs/narr/views.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'docs') diff --git a/docs/narr/views.rst b/docs/narr/views.rst index 548ea5006..f233ee39d 100644 --- a/docs/narr/views.rst +++ b/docs/narr/views.rst @@ -1787,11 +1787,12 @@ view configuration, see :ref:`models_which_implement_interfaces`. Configuring View Security ~~~~~~~~~~~~~~~~~~~~~~~~~ -If an :term:`authorization policy` is active, any :term:`permission` attached -to a :term:`view configuration` found during view lookup will be consulted to -ensure that the currently authenticated user possesses that permission -against the :term:`context` before the view function is actually called. -Here's an example of specifying a permission in a view configuration using +If an :term:`authorization policy` is active, any :term:`permission` +attached to a :term:`view configuration` found during view lookup will +be verified. This will ensure that the currently authenticated user +possesses that permission against the :term:`context` before the view +function is actually called. Here's an example of specifying a +permission in a view configuration using :meth:`pyramid.configuration.Configurator.add_view`: .. code-block:: python -- cgit v1.2.3