#12952: Models history doesn't use verbose names
-------------------------------+------------------------------------
     Reporter:  acangiano      |                    Owner:  nobody
         Type:  Bug            |                   Status:  new
    Component:  contrib.admin  |                  Version:  1.2-beta
     Severity:  Normal         |               Resolution:
     Keywords:                 |             Triage Stage:  Accepted
    Has patch:  1              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  1
-------------------------------+------------------------------------
Changes (by aaugustin):

 * stage:  Design decision needed => Accepted


Comment:

 The objection was "for debug purposes, it would be more useful to have the
 field names, as they are necessarily unique, untranslated, etc."

 In my opinion:
 - uniqueness is a weak argument: if you have two fields with the same
 name, you're just asking for trouble;
 - translation isn't an issue at all: in doubt, just switch the website to
 the default language of your codebase.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/12952#comment:9>
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.

Reply via email to