summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2011-02-26 11:57:26 -0500
committerChris McDonough <chrism@plope.com>2011-02-26 11:57:26 -0500
commitfe164c184edaf810b3c1b4afb757672e2befa2ec (patch)
treeeb956ec0318728c71fc458af89c5aa02d2c3de19
parent3d812457d868434278603441976e91172423e717 (diff)
downloadpyramid-fe164c184edaf810b3c1b4afb757672e2befa2ec.tar.gz
pyramid-fe164c184edaf810b3c1b4afb757672e2befa2ec.tar.bz2
pyramid-fe164c184edaf810b3c1b4afb757672e2befa2ec.zip
it's request_param
-rw-r--r--docs/narr/viewconfig.rst2
-rw-r--r--pyramid/config.py4
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/narr/viewconfig.rst b/docs/narr/viewconfig.rst
index 0a6d9ee61..9b2500a2b 100644
--- a/docs/narr/viewconfig.rst
+++ b/docs/narr/viewconfig.rst
@@ -258,7 +258,7 @@ configured view.
variable) that has a name which matches the supplied value.
If the value supplied has a ``=`` sign in it,
- e.g. ``request_params="foo=123"``, then the key (``foo``) must both exist
+ e.g. ``request_param="foo=123"``, then the key (``foo``) must both exist
in the ``request.params`` dictionary, *and* the value must match the right
hand side of the expression (``123``) for the view to "match" the current
request.
diff --git a/pyramid/config.py b/pyramid/config.py
index 86691c9a1..11770624d 100644
--- a/pyramid/config.py
+++ b/pyramid/config.py
@@ -1121,7 +1121,7 @@ class Configurator(object):
dictionary (an HTTP ``GET`` or ``POST`` variable) that has a
name which matches the supplied value. If the value
supplied has a ``=`` sign in it,
- e.g. ``request_params="foo=123"``, then the key (``foo``)
+ e.g. ``request_param="foo=123"``, then the key (``foo``)
must both exist in the ``request.params`` dictionary, *and*
the value must match the right hand side of the expression
(``123``) for the view to "match" the current request.
@@ -1550,7 +1550,7 @@ class Configurator(object):
dictionary (an HTTP ``GET`` or ``POST`` variable) that has a
name which matches the supplied value. If the value
supplied as the argument has a ``=`` sign in it,
- e.g. ``request_params="foo=123"``, then the key
+ e.g. ``request_param="foo=123"``, then the key
(``foo``) must both exist in the ``request.params`` dictionary, and
the value must match the right hand side of the expression (``123``)
for the route to "match" the current request. If this predicate