If we use __unicode__ (which i'm fine with) then it needs to follow the same resolution path as user.data[] does.
On Monday, April 2, 2012 at 9:25 PM, Anssi Kääriäinen wrote: > On Apr 3, 4:20 am, Donald Stufft <donald.stu...@gmail.com (http://gmail.com)> > wrote: > > If i recall on IRC the decider was to just create a display field (e.g. > > user.data["display"]) that the default profiles can provide (and can be > > overridden by other profiles of course). > > > My problem with this is that for example where I work the display > field would contain '%s, %s (%s)' % (self.lastname, self.firstname, > self.empl_no). I would not like to do that data duplication. If the > 'display' can be a property then fine. But why not go directly for > __unicode__ in that case? > > - Anssi > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com > (mailto:django-developers@googlegroups.com). > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com > (mailto:django-developers+unsubscr...@googlegroups.com). > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
