#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 olaf):
Ok, I changed my patch a little bit. I added a new optional parameter to
the reverse function. If check_default_args is not set(=None), reverse
tries to find a match the standard way, if it will not succeed it tries
one time again including the default_args. If it is set to False, it
behaves just like the current reverse function. If it is set to true, it
will check them from the beginning.
I would like to write those test cases, but I don't know how to use
different url configs. Could you point me to an Howto or give me a small
example, and I will write them.
Thanks
--
Ticket URL: <http://code.djangoproject.com/ticket/15180#comment:3>
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.
