Allow admindocs to show more than just methods that can be called from templates

[Žan Anderle]

contrib.admindocs will only document template tags and functions that can be invoked from templates. Therefore it has limited use. It would be really useful to be able to document all of the functions. contrib.admindocs is a neat way of creating some basic documentation without any extra effort other than docstrings. By adding this feature, this potential could be fulfilled.

There could also be an option to highlight only the functions that can be invoked from templates, in order to support old functionality.

[Tim Graham]

It would be appropriate to raise the issue on the DevelopersMailingList if you want to revisit this design decision.

[Žan Anderle]

Replying to timgraham:

It would be appropriate to raise the issue on the DevelopersMailingList if you want to revisit this design decision.

I just did. Let me know if there is anything else I can/should do.

[Marc Tamlyn]

Accepting as I feel the "quick and dirty documentation tool for the whole dev team" is a more common paradigm than the "documentation tool for template authors only" one.

If however we do relax this, it opens up questions of what else should be included in the constructed docs? Forms? Views? URLs? Managers? Tasks?

At this point you're closer to a customised version of Sphinx's autodoc.

[Žan Anderle]

Just created a PR ​https://github.com/django/django/pull/4939

[Tim Graham <timograham@…>]

In f3dc173:

Fixed #24917 -- Made admindocs display model methods that take arguments.

[Tim Graham <timograham@…>]

In 75143fa1:

Fixed #26182 -- Removed an obsolete (refs #24917) paragraph in admindocs.

[Tim Graham <timograham@…>]

In c5d59173:

[1.9.x] Fixed #26182 -- Removed an obsolete (refs #24917) paragraph in admindocs.

Backport of 75143fa13f4f1ad2be84a103f7ce0eef9d06d3b4 from master