#11559: urlresolvers.reverse do not work with namespaced urls and captured
parameters in parent urlconf
----------------------------------------+-----------------------------------
Reporter: kmik...@gmail.com | Owner: nobody
Status: new | Milestone:
Component: Core framework | Version: SVN
Resolution: | Keywords:
Stage: Someday/Maybe | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
----------------------------------------+-----------------------------------
Comment (by t...@ktrl.com):
I would argue in the opposite direction; that this is not a feature but is
in fact a bug. Since forward URL resolution works completely in this
regard it should be expected that the reverse() method does the same.
Because this is outside of the problem domain of the admin does not mean
it's an invalid use case. I think extending the problem to 'provide some
measure of validation and protection' is adding more to this issue that
necessary. Those of us advanced folks creating modular apps that DRY out a
repeated system or task know that the views in this particular app take a
parameter or **kwargs and per the django norm are expected to write views
correctly. Django already just allows python to handle it by raising an
exception so in that regard there is no difference.
--
Ticket URL: <http://code.djangoproject.com/ticket/11559#comment:10>
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-upda...@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.
