| 59 | | (r'^/articles/2003/$', 'news.views.special_case_2003'), |
|---|
| 60 | | (r'^/articles/(?P<year>\d{4})/$', 'news.views.year_archive'), |
|---|
| 61 | | (r'^/articles/(?P<year>\d{4})/(?P<month>\d{2})/$', 'news.views.month_archive'), |
|---|
| 62 | | (r'^/articles/(?P<year>\d{4})/(?P<month>\d{2})/(?P<day>\d+)/$', 'news.views.article_detail'), |
|---|
| | 59 | (r'^articles/2003/$', 'news.views.special_case_2003'), |
|---|
| | 60 | (r'^articles/(?P<year>\d{4})/$', 'news.views.year_archive'), |
|---|
| | 61 | (r'^articles/(?P<year>\d{4})/(?P<month>\d{2})/$', 'news.views.month_archive'), |
|---|
| | 62 | (r'^articles/(?P<year>\d{4})/(?P<month>\d{2})/(?P<day>\d+)/$', 'news.views.article_detail'), |
|---|
| 212 | | (r'^/articles/(?P<year>\d{4})/$', 'myproject.news.views.year_archive'), |
|---|
| 213 | | (r'^/articles/(?P<year>\d{4})/(?P<month>\d{2})/$', 'myproject.news.views.month_archive'), |
|---|
| 214 | | (r'^/articles/(?P<year>\d{4})/(?P<month>\d{2})/(?P<day>\d+)/$', 'myproject.news.views.article_detail'), |
|---|
| | 215 | (r'^articles/(?P<year>\d{4})/$', 'myproject.news.views.year_archive'), |
|---|
| | 216 | (r'^articles/(?P<year>\d{4})/(?P<month>\d{2})/$', 'myproject.news.views.month_archive'), |
|---|
| | 217 | (r'^articles/(?P<year>\d{4})/(?P<month>\d{2})/(?P<day>\d+)/$', 'myproject.news.views.article_detail'), |
|---|
| 227 | | (r'^/articles/(?P<year>\d{4})/$', 'year_archive'), |
|---|
| 228 | | (r'^/articles/(?P<year>\d{4})/(?P<month>\d{2})/$', 'month_archive'), |
|---|
| 229 | | (r'^/articles/(?P<year>\d{4})/(?P<month>\d{2})/(?P<day>\d+)/$', 'article_detail'), |
|---|
| | 230 | (r'^articles/(?P<year>\d{4})/$', 'year_archive'), |
|---|
| | 231 | (r'^articles/(?P<year>\d{4})/(?P<month>\d{2})/$', 'month_archive'), |
|---|
| | 232 | (r'^articles/(?P<year>\d{4})/(?P<month>\d{2})/(?P<day>\d+)/$', 'article_detail'), |
|---|
| 255 | | Note that an included URLconf receives any captured parameters from parent |
|---|
| 256 | | URLconfs, so the following example is valid:: |
|---|
| | 258 | Note that the regular expressions in this example don't have a ``$`` |
|---|
| | 259 | (end-of-string match character) but do include a trailing slash. Whenever |
|---|
| | 260 | Django encounters ``include()``, it chops off whatever part of the URL matched |
|---|
| | 261 | up to that point and sends the remaining string to the included URLconf for |
|---|
| | 262 | further processing. |
|---|
| | 263 | |
|---|
| | 264 | .. _`Django website`: http://www.djangoproject.com/ |
|---|
| | 265 | |
|---|
| | 266 | Captured parameters |
|---|
| | 267 | ------------------- |
|---|
| | 268 | |
|---|
| | 269 | An included URLconf receives any captured parameters from parent URLconfs, so |
|---|
| | 270 | the following example is valid:: |
|---|