#15180: reverse doesn't check default_args
------------------------------------------+---------------------------------
Reporter: olaf | Owner: nobody
Status: new | Milestone: 1.3
Component: Core framework | Version: 1.3-beta
Resolution: | Keywords: resolve default_args
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 1
Patch needs improvement: 0 |
------------------------------------------+---------------------------------
Comment (by russellm):
I have a background suspicion that this will cause all sorts of havoc with
existing URL lookups -- for example, existing views with default arguments
that *aren't* using the default arguments to differentiate between views.
However, since the patch doesn't have any tests, I can't verify this
quickly.
Marking this as a qualified accepted, the qualification being that the
implementation *must* be backwards compatible with existing uses, and be
tested as such. If that can't be achieved, then we'll need to close
wontfix.
--
Ticket URL: <http://code.djangoproject.com/ticket/15180#comment:2>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
