Positional arguments not passed to view functions in included urlconfs

[Ryan Fugger]

The docs say "An included URLconf receives any captured parameters from parent URLconfs":

​https://docs.djangoproject.com/en/1.4/topics/http/urls/#captured-parameters

But this only works currently for named arguments, not positional ones. I've included a small project demonstrating the issue, with a runnable test case.

[stefantalpalaru]

the fix

[stefantalpalaru]

See the attached patch for a simple fix. I've tried to write a test for regressiontests but gave up in the process.

[stefantalpalaru]

better fix and test case

[stefantalpalaru]

Better patch that only adds the unnamed matches from the parent pattern. I've also added a test.

[Chris Beaven]

This is not a bug -- the docs specifically cover the current behaviour: ​https://docs.djangoproject.com/en/1.4/topics/http/urls/#the-matching-grouping-algorithm.

I can't see how we could introduce this without being backwards incompatible (someone may be using a mix and expecting the conf to ignore the unnamed groups).

[Ryan Fugger]

@SmileyChris, thanks for pointing that out. However, the documentation at that link states that positional arguments will be passed to view functions as long as there are no named arguments. My included project demonstrates that this is not working properly with included urlconfs. I have two suggestions:

1. Have positional arguments passed to views as long as there are no named arguments, even when they were captured before included urlconfs, as per the matching-grouping algorithm documentation at your link.

2. If this is too difficult to implement, update the documentation at:

​https://docs.djangoproject.com/en/1.4/topics/http/urls/#captured-parameters

to say that positional arguments are never passed to views when they are captured before included urlconfs. Also update the matching-grouping algorithm documentation to say this.

Thanks!

[Bas Peschier]

This is a duplicate of #12943 and was recently fixed.