Fixed typo in docs/tutorial03.txt. Thanks, Aggelos Orfanakos
git-svn-id: http://code.djangoproject.com/svn/django/trunk@745 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
6b2226bab8
commit
5595fe2aa6
|
@ -91,8 +91,8 @@ Finally, it calls that ``detail()`` function like so::
|
||||||
detail(request=<HttpRequest object>, poll_id=23)
|
detail(request=<HttpRequest object>, poll_id=23)
|
||||||
|
|
||||||
The ``poll_id=23`` part comes from ``(?P<poll_id>\d+)``. Using
|
The ``poll_id=23`` part comes from ``(?P<poll_id>\d+)``. Using
|
||||||
``(?<name>pattern)`` "captures" the text matched by ``pattern`` and sends it as
|
``(?P<name>pattern)`` "captures" the text matched by ``pattern`` and sends it
|
||||||
a keyword argument to the view function.
|
as a keyword argument to the view function.
|
||||||
|
|
||||||
Because the URL patterns are regular expressions, there really is no limit on
|
Because the URL patterns are regular expressions, there really is no limit on
|
||||||
what you can do with them. And there's no need to add URL cruft such as
|
what you can do with them. And there's no need to add URL cruft such as
|
||||||
|
|
Loading…
Reference in New Issue