#4915: A smarter resolver: try to disambiguate URL patterns
-------------------------------+--------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mtredinnick
Status: new | Component: Core framework
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 1 | Needs_better_patch: 1
-------------------------------+--------------------------------------------
Comment (by [EMAIL PROTECTED]):
Replying to [comment:6 SmileyChris]:
> Current behaviour is that `url02` isn't flawed. ''Forward'' resolving
ignores positional args if any kwargs are given, but the reverse resolver
accepts ''both'' (falling back to using positional arguments if a keyword
arg is not present but required).
Hmm, that honestly seems kind of broken. The purpose of the reverse
resolver is to generate URLs which will map to the supplied view and
parameters - hence, generating a URL which doesn't resolve back to the
parameters that you specified is incorrect behavior. It's probably better
to refuse to generate a URL at all than to generate one which won't behave
as desired.
--
Ticket URL: <http://code.djangoproject.com/ticket/4915#comment:7>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
