#19864: No standard method of indicating import paths in documentation
--------------------------------------+------------------------------------
Reporter: davesque@… | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.4
Severity: Normal | Resolution:
Keywords: import paths | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by carljm):
* stage: Unreviewed => Accepted
Comment:
I agree that it would be better if the full import path were more
consistently available in the reference documentation. There will need to
be some decisions made about how/where to display it (for instance, in
your example case I think it would be even clearer if it just said `class
django.template.response.SimpleTemplateResponse` rather than `class
SimpleTemplateResponse`.)
The next thing needed to get this "initiative" rolling is a proposed patch
to the docs!
--
Ticket URL: <https://code.djangoproject.com/ticket/19864#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
