From a5ffd62175a09402fbe37ec8c2077873e0a35903 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sat, 18 Dec 2010 15:12:46 -0500 Subject: model->resource; make docs render without warnings --- docs/narr/handlers.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/narr/handlers.rst') diff --git a/docs/narr/handlers.rst b/docs/narr/handlers.rst index f6e658cf0..5b6f71984 100644 --- a/docs/narr/handlers.rst +++ b/docs/narr/handlers.rst @@ -100,7 +100,7 @@ Using :meth:`~pyramid.config.Configurator.add_handler` When calling :meth:`~pyramid.config.Configurator.add_handler`, an ``action`` is required in either the route pattern or as a keyword argument, but **cannot appear in both places**. A ``handler`` argument must also be -supplied, which can be either a :term:`resource specification` or a Python +supplied, which can be either a :term:`asset specification` or a Python reference to the handler class. Additional keyword arguments are passed directly through to :meth:`pyramid.config.Configurator.add_route`. @@ -112,7 +112,7 @@ For example: config.add_handler('hello', '/hello/{action}', handler='mypackage.handlers:MyHandler') -In larger applications, it is advised to use a :term:`resource specification` +In larger applications, it is advised to use a :term:`asset specification` with :meth:`~pyramid.config.Configurator.add_handler` to avoid having to import every handler class. -- cgit v1.2.3