From e6b6a600ffa7d04e910887311832681c000406f5 Mon Sep 17 00:00:00 2001 From: Casey Duncan Date: Mon, 22 Nov 2010 18:30:33 -0700 Subject: XXX Add an additional explaining sentence to clarify the chain of 'implieds' in the hybrid example. Confirm this is correct XXX --- docs/narr/hybrid.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/narr/hybrid.rst b/docs/narr/hybrid.rst index c57bf0fc3..6fa6037c1 100644 --- a/docs/narr/hybrid.rst +++ b/docs/narr/hybrid.rst @@ -207,8 +207,11 @@ the matched route's configuration. Because the pattern of the above route ends with ``*traverse``, when this route configuration is matched during a request, :app:`Pyramid` will attempt to use :term:`traversal` against the :term:`root` object -implied by the :term:`root factory` implied by the route's -configuration. Once :term:`traversal` has found a :term:`context`, +implied by the :term:`root factory` that is implied by the route's +configuration. Since no ``root_factory`` argument is explicitly specified +for this route, this will either be the *global* root factory +for the application, or the *default* root factory. +Once :term:`traversal` has found a :term:`context`, :term:`view lookup` will be invoked in almost exactly the same way it would have been invoked in a "pure" traversal-based application. -- cgit v1.2.3