#18129: Capitalization of verbose_name bad design decision. Why waste computer
power.
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: 1.4
Component: Uncategorized | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: capitalize | Unreviewed
verbose_name | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by adrian):
* status: new => closed
* resolution: => wontfix
Comment:
We rely on verbose_name *not* having initial caps in your models, and we
add caps wherever appropriate. It wouldn't work the other way around
(expecting models to have initial caps, and lower-casing them when
appropriate) because a verbose_name might be an all-caps acronym that
shouldn't *ever* be lower-cased. And displaying verbose_names without an
upper case just looks ugly. We have standards. :-)
--
Ticket URL: <https://code.djangoproject.com/ticket/18129#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
