#14018: Introduce class_plural %-substitution placeholder for related_name of
ForeignKey/ManyToManyField
---------------------------------------------------+------------------------
          Reporter:  puxlit                        |         Owner:  nobody     
                                                   
            Status:  new                           |     Milestone:  2.0        
                                                   
         Component:  Database layer (models, ORM)  |       Version:  SVN        
                                                   
        Resolution:                                |      Keywords:  
related_name, ManyToManyField, ForeignKey, abstract base class
             Stage:  Design decision needed        |     Has_patch:  1          
                                                   
        Needs_docs:  0                             |   Needs_tests:  0          
                                                   
Needs_better_patch:  1                             |  
---------------------------------------------------+------------------------
Changes (by puxlit):

  * milestone:  1.3 => 2.0

Comment:

 Replying to [comment:1 anonymous] and [comment:2 mk]:
 Good point; I hadn't considered `verbose_name_plural`s with multiple
 and/or internationalised words.

 Replying to [comment:3 lrekucki]:
 That's a rather elegant solution. I agree that it's more of a nice touch
 than a must-have feature, but I make use of this patch in my code, and
 don't believe there's any harm in including it.

 Thanks for all the suggestions! I'm presently working on a patch with
 updated documentation and a set of test cases.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/14018#comment:4>
Django <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 django-upda...@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