id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
3422	url configuration: include in combination with extra options messes up reverse resolving	Jeroen van Dongen <jeroen at jkwadraat.net>	nobody	"Say I have a main urls.py like this:
{{{
urlpatterns = patterns('',
    (r'^xxx/weblog/',        include('myapps.blog.urls'), {'weblog_id': 'foo'}),
    (r'^yyy/weblog/',        include('myapps.blog.urls'), {'weblog_id': 'bar'}),
)
}}}

and in 'myapps.blog.urls' something like this:

{{{
urlpatterns = patterns('',
    (r'^$',        'myapps.blog.views.index'),
)
}}}

Then when a I visit '/yyy/weblog/', the blog's index view would get the parameter 'weblog_id' with 
value 'bar' and presents the correct weblog (i.e. the resolver correctly finds that it needs to
use the second line from urls.py).

However when I then do a reverse url lookup in my view, passing weblog_id='bar' as parameter,
it will latch onto the first entry and return '/xxx/weblog/' instead of '/yyy/weblog'.

Apperently the reverse resolver does not take the extra options from urls.py into account during resolving, 
while the forward resolver does."	New feature	closed	Core (Other)	dev	Normal	wontfix	urls.py reverse resolver extra_options		Accepted	0	0	0	0	0	0