{{{
re_path(r'admin/doc/',include('django.contrib.admindocs.urls'),
namespace='docs')
}}}
It requires an easy fix: to add an app_name to admindocs.
--
Ticket URL: <https://code.djangoproject.com/ticket/31848>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => needsinfo
* easy: 1 => 0
Comment:
Is there any reason to use namespaced `django.contrib.admindocs.views`?
Paths contain the `django-admindocs-` prefix so you shouldn't have
conflicts. Moreover proposed change is backward incompatible.
--
Ticket URL: <https://code.djangoproject.com/ticket/31848#comment:1>
Comment (by Marcelo Cardoso):
Yes, there is. For instance, when using admindocs, everything under it
falls into the empty namespace category, which is annoying if one is
trying to keep that section organized to the end user. Of course, there
are workarounds, but that would save other devs some time working around
it.
--
Ticket URL: <https://code.djangoproject.com/ticket/31848#comment:2>
* resolution: needsinfo => wontfix
Comment:
Yes, so I don't think it's worth backward incompatible change that will
force other users (that use `admindocs` in custom pages) to update their
URLs. You can always force namespaced views with:
{{{
urlpatterns = [
...,
path('admin/doc/',include((django.contrib.admindocs.urls.urlpatterns,
'admindocs'), namespace='docs'))
...,
]
}}}
if it's really important to you.
--
Ticket URL: <https://code.djangoproject.com/ticket/31848#comment:3>