#18129: Capitalization of verbose_name bad design decision. Why waste computer
power.
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.4
Component: Uncategorized | Resolution:
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 |
-------------------------------------+-------------------------------------
Comment (by Evil Clay <clay.evil@…>):
I'm sorry, i meant no harm with the title, just an attempt to describe
relevant points in a short line. I like django very much, I programed in
java for 5 years using Apache Wicket. But i can say that in many ways
django is better. So thank you all, you have done a great job, and sorry
for this "spam" comment, just wanted to set thing straight.
to add something to the matter at hand, i understand the backward issue i
saw the changes in admin where all verbose_names were changed to
lowercase. But i feel this is something that has to be done sooner or
later.
Maybe you could add an default setting that will ensure current behavior
but will also rise an deprecation warning on server start and you can
override this setting you a project local settings file to turn off the
Capitalization and this will also silence the deprecation warning.
As for the admin part, probably a lot of manual work to capitalize the
verbose_names. I could help with that.
--
Ticket URL: <https://code.djangoproject.com/ticket/18129#comment:2>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
