On Mon, Mar 18, 2013 at 10:23 AM, julianb <[email protected]> wrote: > Well, at the moment, as far as I am aware, you can't. The first URL will > match everything all the time, not giving the other views a chance to kick > in. > > So I propose some kind of URL fallthrough. The view could do > > raise UrlNotMatched > > and the dispatcher goes to the next possible matching view. > > Would that be good? Any thoughts?
Hi Julian, I'd rather not add this to the framework, as it's already possible with a "wrapper" view (as others have suggested). And on a more theoretical level, it introduces more coupling between URL patterns and views. Adrian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
