#2977: [patch] Better handling of regular expressions for reverse urlresolver
---------------------------+------------------------------------------------
Reporter: SmileyChris | Owner: adrian
Status: new | Component: Core framework
Version: | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------+------------------------------------------------
Comment (by SmileyChris):
Yea, I should have written separate patches. Next time ;)
Re fix 2, I'm probably blowing hot air, you already said it's going stay
as-is in the other ticket but I'm still not sure why you think mixing
keyword and positional arguments is useful if it doesn't work for a
forward resolution.
In the form of a question: Why should a `reverse` match a
`RegexURLPattern` which won't call its view the same arguments which
`reverse` received?
Fix 4 is because I didn't want to tackle the difficult types of extension
notation, notably lookahead/behind assertions and named backreferences.
Note, the patch also handles non-grouping parenthesis.
--
Ticket URL: <http://code.djangoproject.com/ticket/2977#comment:11>
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
-~----------~----~----~----~------~----~------~--~---
