From e71e4fc111fe8846ba5050557e6d0e74cd3ce643 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=89ric=20Araujo?= Date: Tue, 14 Jan 2020 17:12:45 -0500 Subject: make two missed lines even longer --- docs/narr/urldispatch.rst | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) (limited to 'docs/narr') diff --git a/docs/narr/urldispatch.rst b/docs/narr/urldispatch.rst index 83a186aea..c41224e99 100644 --- a/docs/narr/urldispatch.rst +++ b/docs/narr/urldispatch.rst @@ -1130,10 +1130,8 @@ Then we use that new keyword argument with :meth:`~pyramid.config.Configurator.a When the route is requested, Pyramid instantiates the ``AnyOfPredicate`` class using the value passed to the ``any_of`` argument. The resulting instance is a :term:`predicate`. It will determine whether incoming requests satisfy its condition. -In the example above, a request for ``/three`` would match the route's URL pattern and satisfy the route's predicate -because ``three`` is one of the allowed values, so the route would be matched. -However a request for ``/millions`` will -match the route's URL pattern but would not satisfy the route's predicate, and the route would not be matched. +In the example above, a request for ``/three`` would match the route's URL pattern and satisfy the route's predicate because ``three`` is one of the allowed values, so the route would be matched. +However a request for ``/millions`` will match the route's URL pattern but would not satisfy the route's predicate, and the route would not be matched. A custom route predicate may also *modify* the ``match`` dictionary. For instance, a predicate might do some type conversion of values: -- cgit v1.2.3