#9176: NoReverseMatch for optional arguments
-----------------------------------------------------+----------------------
Reporter: [EMAIL PROTECTED] | Owner: mtredinnick
Status: new | Milestone:
Component: Core framework | Version: 1.0
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------+----------------------
Changes (by mtredinnick):
* stage: Accepted => Design decision needed
Comment:
Hmm ... thinking about this some more, it's not so clear that it is worth
doing for this one particular case. It's a bit of an edge case because
it's not guaranteed to work in all cases: nested groups won't work for
either positional arguments or keyword arguments, for example. So it's not
necessarily true that just because your view received a particular set of
keyword or positional arguments that you can pass all of those back to
`reverse()` and have it resolve to something. Implementing just this one
case (None values) will then lead to people trying it with nested values
and other odd combinations and we'll be at this forever.
Putting in "design decision needed", because I don't want to rush to (a
different) judgement. But having played with writing some tests for a few
minutes, I'm inclined to think it's not a good idea.
--
Ticket URL: <http://code.djangoproject.com/ticket/9176#comment:6>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
