#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 anonymous):
I've attached a patch that tweaks an existing template test to cover the
new reverse resolver, as well as relaxing the equivalence check a bit (by
converting all parameters to strings) and fixing a few lurking Unicode
bugs that popped up when I was debugging the regression tests.
There's a catch, though: one of the tests ('url02') fails. However, this
appears to not be an issue with my modifications, but rather some sort of
latent bug in the resolver that I've just happened to expose!
Specifically, patterns containing keyword arguments are losing their
positional arguments. As the expanded reverse resolver actually checks to
make sure that the URL it constructs has the same parameters as it got
passed in, it (appropriately) rejects the URL that it constructs for
patterns containing both types of arguments. I've opened #4925 to address
this issue.
--
Ticket URL: <http://code.djangoproject.com/ticket/4915#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
