From b887aaa95a88fab020fb75d4d5fb46c35119365b Mon Sep 17 00:00:00 2001 From: Casey Duncan Date: Sun, 21 Nov 2010 10:07:42 -0700 Subject: clarify sentence about nonsensical replacement markers --- docs/narr/urldispatch.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs') diff --git a/docs/narr/urldispatch.rst b/docs/narr/urldispatch.rst index 3ac3bcf27..a072f87a8 100644 --- a/docs/narr/urldispatch.rst +++ b/docs/narr/urldispatch.rst @@ -268,10 +268,10 @@ and the match result will be ``{'name': 'biz', 'ext': 'html'}``. This occurs because the replacement marker ``{name}`` has a literal part of ``.`` (period) between the other 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 a custom regular expression to restrict what a marker -captures. +It is possible to use two replacement markers without any literal +characters between them, for instance ``/{foo}{bar}``. However, this +would be a nonsensical pattern without specifying a custom regular +expression to restrict what each marker captures. Segments must contain at least one character in order to match a segment replacement marker. For example, for the URL ``/abc/``: -- cgit v1.2.3