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
8470	Documentation for verbose field names could suggest a DRY way to define verbose_name for foreign keys	amiroff	nobody	"At http://www.djangoproject.com/documentation/model-api/#verbose-field-names ,

Documentation states that we can use the following:

{{{
poll = models.ForeignKey(Poll, verbose_name=""the related poll"")
}}}

If you already have verbose_name defined under Meta class of Poll object, this way of defining it twice does not obey DRY principle.
In this case using the following way to specify verbose_name would improve the documentation:

{{{
poll = models.ForeignKey(Poll, verbose_name=Poll._meta.verbose_name)
}}}

"		closed	Documentation	dev		wontfix	verbose_name foreign key, foreign_key, ForeignKey	amiroff@…	Unreviewed	0	0	0	0	0	0