#7724: get_FIELD_display in backend doesn't respect FIELD's name or verbose_name
---------------------------------------+------------------------------------
          Reporter:  CaptainCapacitor  |         Owner:  nobody                 
               
            Status:  closed            |     Milestone:                         
               
         Component:  Admin interface   |       Version:  SVN                    
               
        Resolution:  invalid           |      Keywords:  admin, get_FIELD_*, 
name, verbose name
             Stage:  Unreviewed        |     Has_patch:  0                      
               
        Needs_docs:  0                 |   Needs_tests:  0                      
               
Needs_better_patch:  0                 |  
---------------------------------------+------------------------------------
Changes (by mtredinnick):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 There's nothing to suggest it should behave like this. You're hoping it
 might, but it isn't really worth the extra code when there's already a way
 to set the title. When you use a function in the `list_display` list it
 uses the  `short_description` attribute on the function for the title,
 otherwise a reasonable default is used. This is documented and the
 versions of `get_FIELD_display()` created automatically are no different
 int his respect.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/7724#comment:1>
Django Code <http://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
-~----------~----~----~----~------~----~------~--~---

Reply via email to