#16774: Backtracking URL resolver
-------------------------------------+-------------------------------------
Reporter: nbstrite | Owner: nobody
Type: New | Status: new
feature | Component: HTTP handling
Milestone: | Severity: Normal
Version: 1.3 | Keywords:
Resolution: | Has patch: 0
Triage Stage: Design | Needs tests: 0
decision needed | Easy pickings: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by russellm):
@mrmachine -- Github pull requests are an accepted form of contribution.
I'm not 100% certain that this is laid out in our contribution guide; if
it isn't, it should be. We have official mirrors on Github and BitBucket
for a reason. The link provided can be trivially used to show a patch
(click on the "diff" button above the changelist).
As for the issue itself: DDN is the right result, but I'm not sure it's
for the right reason. My concern is over backwards compatibility -- a
valid URLpatterns file that currently rejects a request could, if this
change were adopted, result in a view actually being served. I'm not
entirely certain that this is a bad thing -- it's really an ambiguity of
the original URLpattern -- but it's worth some deeper consideration.
--
Ticket URL: <https://code.djangoproject.com/ticket/16774#comment:2>
Django <https://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
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
