Having read contributing.txt not enough, I added the following comment to the ticket (reopening it as well) in response to jacob's comment. mtredinnick kindly advised me using the list instead of reopening it:
---- > Yes, we're sure this is wontfix. Could you please give a short rationale on this given that having custom labels is not trivial as you did think before. The solution, as SmileyChris explained, involves some code duplication (maybe more code duplicated than the actual bits used for getting the custom label itself) I have a class Foo that have a user = ForeignKey(User) and would like to choose users for Foo instances by their full name instead of by their username. User here is the standard class from django.contrib.auth and so it's outside my control. The needing of displaying full names instead of usernames in a ModelChoiceField for django.contrib.auth.models.User doesn't seem so uncommon to me. ---- Regards, maykel [1] http://code.djangoproject.com/ticket/4620#comment:8 [2] http://code.djangoproject.com/ticket/4620#comment:6 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
