summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorBen Bangert <ben@groovie.org>2010-11-18 23:25:14 -0800
committerBen Bangert <ben@groovie.org>2010-11-18 23:25:14 -0800
commit15c258849aa54eb99d272fbbef0e9c3d911d2cca (patch)
tree707f8410c39d7f199aecb5ebd2e9b1e527cf0f06 /docs
parent0f89f91a5bf4f26734235d01e81dffc77abba9c4 (diff)
downloadpyramid-15c258849aa54eb99d272fbbef0e9c3d911d2cca.tar.gz
pyramid-15c258849aa54eb99d272fbbef0e9c3d911d2cca.tar.bz2
pyramid-15c258849aa54eb99d272fbbef0e9c3d911d2cca.zip
There is no pattern_regexes.
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/urldispatch.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/narr/urldispatch.rst b/docs/narr/urldispatch.rst
index ae0ecf629..a86041e55 100644
--- a/docs/narr/urldispatch.rst
+++ b/docs/narr/urldispatch.rst
@@ -270,8 +270,8 @@ replacement marker ``:ext``.
It is possible to use two replacement markers without any literal characters
between them, for instance ``/{foo}{bar}``. This would be a nonsensical pattern
-without specifying any ``pattern_regexes`` to restrict valid values of each
-replacement marker.
+without specifying a custom regular expression to restrict what a marker
+captures.
Segments must contain at least one character in order to match a
segment replacement marker. For example, for the URL ``/abc/``: