diff options
Diffstat (limited to 'docs/zcml')
| -rw-r--r-- | docs/zcml/configure.rst | 6 | ||||
| -rw-r--r-- | docs/zcml/forbidden.rst | 4 | ||||
| -rw-r--r-- | docs/zcml/notfound.rst | 4 | ||||
| -rw-r--r-- | docs/zcml/route.rst | 2 | ||||
| -rw-r--r-- | docs/zcml/scan.rst | 2 | ||||
| -rw-r--r-- | docs/zcml/static.rst | 2 | ||||
| -rw-r--r-- | docs/zcml/subscriber.rst | 2 | ||||
| -rw-r--r-- | docs/zcml/view.rst | 2 |
8 files changed, 12 insertions, 12 deletions
diff --git a/docs/zcml/configure.rst b/docs/zcml/configure.rst index db8219a2d..cab8ec204 100644 --- a/docs/zcml/configure.rst +++ b/docs/zcml/configure.rst @@ -4,7 +4,7 @@ ------------- Because :term:`ZCML` is XML, and because XML requires a single root -tag for each document, every ZCML file used by :mod:`pyramid` must +tag for each document, every ZCML file used by :app:`Pyramid` must contain a ``configure`` container directive, which acts as the root XML tag. It is a "container" directive because its only job is to contain other directives. @@ -40,9 +40,9 @@ the ``configure`` start tag. Using the ``http://pylonshq.com/pyramid`` namespace as the default XML namespace isn't strictly necessary; you can use a different default namespace as the default. However, if you do, the declaration tags -which are defined by :mod:`pyramid` such as the ``view`` declaration +which are defined by :app:`Pyramid` such as the ``view`` declaration tag will need to be defined in such a way that the XML parser that -:mod:`pyramid` uses knows which namespace the :mod:`pyramid` tags are +:app:`Pyramid` uses knows which namespace the :mod:`pyramid` tags are associated with. For example, the following files are all completely equivalent: diff --git a/docs/zcml/forbidden.rst b/docs/zcml/forbidden.rst index 330df3c2e..f5b1b4644 100644 --- a/docs/zcml/forbidden.rst +++ b/docs/zcml/forbidden.rst @@ -3,7 +3,7 @@ ``forbidden`` ------------- -When :mod:`pyramid` can't authorize execution of a view based on +When :app:`Pyramid` can't authorize execution of a view based on the :term:`authorization policy` in use, it invokes a :term:`forbidden view`. The default forbidden response has a 401 status code and is very plain, but it can be overridden as necessary using the @@ -11,7 +11,7 @@ very plain, but it can be overridden as necessary using the .. warning:: - The ``forbidden`` ZCML directive is deprecated in :mod:`pyramid` + The ``forbidden`` ZCML directive is deprecated in :app:`Pyramid` version 1.3. Instead, you should use the :ref:`view_directive` directive with a ``context`` that names the :exc:`pyramid.exceptions.Forbidden` class. See diff --git a/docs/zcml/notfound.rst b/docs/zcml/notfound.rst index 0e1652708..54826ea17 100644 --- a/docs/zcml/notfound.rst +++ b/docs/zcml/notfound.rst @@ -5,13 +5,13 @@ .. warning:: - The ``notfound`` ZCML directive is deprecated in :mod:`pyramid` + The ``notfound`` ZCML directive is deprecated in :app:`Pyramid` version 1.0. Instead, you should use the :ref:`view_directive` directive with a ``context`` that names the :exc:`pyramid.exceptions.NotFound` class. See :ref:`changing_the_notfound_view` form more information. -When :mod:`pyramid` can't map a URL to view code, it invokes a +When :app:`Pyramid` can't map a URL to view code, it invokes a :term:`not found view`. The default not found view is very plain, but the view callable used can be configured via the ``notfound`` ZCML tag. diff --git a/docs/zcml/route.rst b/docs/zcml/route.rst index ad746cba7..ed849e3c1 100644 --- a/docs/zcml/route.rst +++ b/docs/zcml/route.rst @@ -24,7 +24,7 @@ Attributes ``factory`` The :term:`dotted Python name` to a function that will generate a - :mod:`pyramid` context object when this route matches. + :app:`Pyramid` context object when this route matches. e.g. ``mypackage.models.MyFactoryClass``. If this argument is not specified, a default root factory will be used. diff --git a/docs/zcml/scan.rst b/docs/zcml/scan.rst index 103098b9f..cbf797e1c 100644 --- a/docs/zcml/scan.rst +++ b/docs/zcml/scan.rst @@ -5,7 +5,7 @@ To make use of :term:`configuration decoration` decorators, you must perform a :term:`scan`. A scan finds these decorators in code. The -``scan`` ZCML directive tells :mod:`pyramid` to begin such a scan. +``scan`` ZCML directive tells :app:`Pyramid` to begin such a scan. Attributes ~~~~~~~~~~ diff --git a/docs/zcml/static.rst b/docs/zcml/static.rst index 815e332c8..164e7400c 100644 --- a/docs/zcml/static.rst +++ b/docs/zcml/static.rst @@ -5,7 +5,7 @@ Use of the ``static`` ZCML directive or allows you to serve static resources (such as JavaScript and CSS files) within a -:mod:`pyramid` application. This mechanism makes static files +:app:`Pyramid` application. This mechanism makes static files available at a name relative to the application root URL. Attributes diff --git a/docs/zcml/subscriber.rst b/docs/zcml/subscriber.rst index c04aecff2..d584f1e02 100644 --- a/docs/zcml/subscriber.rst +++ b/docs/zcml/subscriber.rst @@ -4,7 +4,7 @@ -------------- The ``subscriber`` ZCML directive configures an :term:`subscriber` -callable to listen for events broadcast by the :mod:`pyramid` web +callable to listen for events broadcast by the :app:`Pyramid` web framework. Attributes diff --git a/docs/zcml/view.rst b/docs/zcml/view.rst index 8117e8ea6..6e67b4c56 100644 --- a/docs/zcml/view.rst +++ b/docs/zcml/view.rst @@ -3,7 +3,7 @@ ``view`` -------- -A ``view`` declaration directs :mod:`pyramid` to create a single +A ``view`` declaration directs :app:`Pyramid` to create a single :term:`view configuration` registration in the current :term:`application registry`. |