#4915: A smarter resolver: try to disambiguate URL patterns
-------------------------------+--------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Core framework
Version: SVN | Resolution:
Keywords: | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------+--------------------------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
You'll need to include some explanation of how your resolver fixes the
existing problems, I think.
For example, if I have two different URL patterns both taking an integer
as a pattern and both calling a particular generic view (with, say, some
extra default args in each case), I don't see how this differentiates
between them. Since the parameter lists and view functions are identical
in the two cases, there ''is'' no way to differentiate sans some extra
information like a name. So you cannot eliminate the need for named
patterns entirely (which was precisely why they were introduced).
If you are also trying to fix some other problem, perhaps including some
tests to show what you are fixing would help with review. At the moment,
the patch isn't too clear.
--
Ticket URL: <http://code.djangoproject.com/ticket/4915#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
