python manage.py routes
--
Ticket URL: <https://code.djangoproject.com/ticket/28800>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by Tim Graham):
[https://github.com/django-extensions/django-extensions django-extensions]
has a `show_urls` command which "produce a tab-separated list of
(url_pattern, view_function, name) tuples for a project." I'm not sure
that this needs to be incorporated into Django itself.
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:1>
Comment (by Martín Peveri):
I understand, but I depend on an extension. Tell me if you consider it to
integrate it into the framework and I could send an RP. Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:2>
* cc: Keryn Knight (added)
Comment:
Can I suggest that its worth taking to the developers mailing list to
discuss this possibility? As an anecdotal datapoint, I know I semi-
frequently make use such a command when coming into a project which I've
not previously been heavily involved with. The flat output (vs traversing
a list of `include()` usages) gives a decent overview on what's what, and
the `contrib.admindocs` package already provides a similar overview if
installed into the admin.
It also isn't a **huge** amount of new work (in my mind, because
[https://github.com/kezabelle/django-unfurl I wrote a similar thing to the
django-extensions command]) precisely because it can depend on the same
functions admindocs does. So the maintenance burden is arguably ''mostly''
already in place.
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:3>
Comment (by Martín Peveri):
I like what I say Keryn Knight. If approved, I could work on the ticket
and send a PR.
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:4>
* stage: Unreviewed => Someday/Maybe
* component: Core (URLs) => Core (Management commands)
Comment:
Someone could try to get a consensus on the DevelopersMailingList about
this. I've never had a need for it myself. A rough criteria I've used for
thinking about whether or not something should be in core is whether 80%
of projects use it. The existence of an implementation in django-
extensions demonstrates this can live as a third-party library which seems
sufficient to me.
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:5>
* owner: nobody => Xavier Tilley
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:6>
* stage: Someday/Maybe => Accepted
Comment:
Discussion at DjangoCon US 2022 suggests it would be a popular enough
feature.
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:7>
* cc: Adam Johnson (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:8>
Comment (by Tom Carrick):
This looks very similar to the new `GeneratedField` - is there still some
value here?
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:9>
Comment (by Natalia Bidart):
Discussion in the forum where consensus seems quite clear:
https://forum.djangoproject.com/t/should-the-show-urls-command-be-part-of-
djangos-standard-library/20739
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:9>
Comment (by Xavier Tilley):
I have the feature finished I just haven't had time to finished up the
tests and documentation. Hopefully my day job will slow down a bit and I
can get a PR in next month.
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:10>
* owner: Xavier Tilley => Keanya Phelps
--
Ticket URL: <https://code.djangoproject.com/ticket/28800#comment:11>