id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
19864	No standard method of indicating import paths in documentation	davesque@…	nobody	"I've been using Django for about a year now and there's something about the Django documentation that's always seemed inconvenient to me.

If you're ever reading about a class, function, etc. in docs, it's rarely obvious where to import that resource from.  The module path is almost never indicated a consistent or obvious way.

For example, take a look at this doc page:

https://docs.djangoproject.com/en/dev/ref/template-response/

What I would expect is that, directly above [https://docs.djangoproject.com/en/dev/ref/template-response/#django.template.response.SimpleTemplateResponse this] heading or somewhere similar, the full import path of the class would be indicated in some way.  Perhaps like this:

...
module: {{{django.template.response}}}

'''''class'' SimpleTemplateResponse'''
...

...or something like that.  I'm aware of the hash links next to each heading which contain the full import path.  This is fine, but that information should not be hidden.  It should be on the page in plain view.

I think we should launch an initiative to fix this problem with usability in the Django docs."	Cleanup/optimization	closed	Documentation	1.4	Normal	duplicate	import paths		Accepted	0	0	0	0	0	0