It appears as though when using Python3.3 and Django 1.6dev you should use __str__ and not __unicode__. __unicode__ seems to be gone from Python3.3
On Tuesday, February 12, 2013 4:45:33 PM UTC-5, David wrote: > > I am working through the tutorial and find that the *def > __unicode__(self):* command to give an object a readable name in admin is > not working. I am cutting code from the tutorial. When I access the > detail screen in /admin/ all I see is [table name] object and not the name > I defined in def __unicode__(self): return: self.name > > I am working with the 1.6dev release in a 64bit Win7 environment. > > Is this a known issue with dev? I have searched Django users without > success. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
