#9176: NoReverseMatch for optional arguments
-----------------------------------------------------+----------------------
Reporter: [EMAIL PROTECTED] | Owner: mtredinnick
Status: closed | Milestone:
Component: Core framework | Version: 1.0
Resolution: wontfix | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------+----------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
Due to the nested groups issue mentioned in the previous comment, it isn't
possible to always pass the arguments you receive from URL resolution back
to reverse without looking at them. The particular issue describe in the
initial description here is easy enough to work around in the calling code
(delete any keys with None as the value) and I don't really want to add
special cases that aren't universally applicable to the reverse-handling
-- it will lead to lots of questions about why one case is supported and
another isn't, etc.
So the rule is that just as it is now: you must pass in the exact set of
arguments to match against and they must have valid values. Sorry, I
realise this isn't ideal, but we can't have a perfect solution here
without adding lots of extra code and it doesn't seem worth it to me.
--
Ticket URL: <http://code.djangoproject.com/ticket/9176#comment:7>
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
-~----------~----~----~----~------~----~------~--~---
