For example, within myproject.urls:
urlpatterns = (
url(r'', include('.myapp.urls')),
)
.. becomes equivalent to::
urlpatterns = (
url(r'', include('myproject.myapp.urls')),
)
Whilst a contrived example, this can make heavy-nested apps look far, far
cleaner. For example, within myproject.foo.foo_bar.foo_bar_baz.urls, one
only needs to include .foo_bar_baz_qux.urls to get to the "next" level,
rather than the significantly more unwieldy
myproject.foo.foo_bar.foo_bar_baz.foo.bar_baz_qux.urls.
----
What do you think of this proposal from
https://code.djangoproject.com/ticket/26288? I don't know if "nested apps"
are very common and/or something that should be promoted with a change like
this.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" 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].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/5a92150c-4969-4432-b47b-0a02ce889312%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
