#25907: Alternative Way of Specifying URL Patterns
-----------------------------+--------------------------------------
Reporter: srkunze | Owner: nobody
Type: New feature | Status: closed
Component: Core (URLs) | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by timgraham):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
You could propose it on the DevelopersMailingList (I couldn't find a past
discussion from a quick seach), but I doubt we'd want to add another way
of defining URLs. If you really want this in your own projects, you could
possibly write an implantation that lives in each app's `urls.py` file and
"autodiscovers" the URLs defined by your views according to whatever
convention you want to use.
--
Ticket URL: <https://code.djangoproject.com/ticket/25907#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.7e58604bf044ac91059d359c95242acb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
