#9123: URL Resolver tag chokes with verbose regex in the urlconf
--------------------------------------+-------------------------------------
Reporter: programmerq | Owner: nobody
Status: closed | Milestone:
Component: Template system | Version: 1.0
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by mtredinnick):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
Backwards-compatible doesn't mean that it necessarily continues to work
for things it wasn't originally designed for that just happened to work by
accident. It's unfortunate that there were some of these accidental cases
that people were relying on, but there's nothing that can be done about
that.
The reverse resolver does explicitly exclude (?x) and raises an
appropriately descriptive error message. It initially appeared to
complicate the code too much to handle that, but if you want to write a
patch that isn't too intrusive, it would certainly be nice to include it.
Closing this for now, since the reverse resolver works as expected. If you
do write a patch, please, by all means, open a new ticket and attach it.
--
Ticket URL: <http://code.djangoproject.com/ticket/9123#comment:1>
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-updates@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
