__unicode__ is called when unicode(ModelInstance) is called. __str__ is called when str(ModelInstance) is called.
Internally, if you only define __unicode__, then Django will provide __str__ for you (see http://code.djangoproject.com/browser/django/trunk/django/db/models/base.py#L277 for the nitty-gritty) Basically, it's good practice to only provide a __unicode__ method and leave __str__ well alone, since you really should always be dealing with unicode strings when interacting with (potentially non-ASCII) data. Thus, you shouldn't type cast any data directly to str() without first knowing exactly what you're doing in the process. On Mar 17, 11:42 am, TP <tommi.pres...@gmail.com> wrote: > I am currently running through the first tutorial on the django > projects site. > > When I have added the __unicode__() method to my models I don't see > any change in how they're represented. > > I am using Django 1.0.2 So an old version is not the problem. > > My models.py looks like this: > > from django.db import models > import datetime > > class Poll(models.Model): > question = models.CharField(max_length=200) > pub_date = models.DateTimeField('date published') > def __str__(self): > return self.question > def was_published_today(self): > return self.pub_date.date() == datetime.date.today() > > class Choice(models.Model): > poll = models.ForeignKey(Poll) > choice = models.CharField(max_length=200) > votes = models.IntegerField() > def __str__(self): > return self.choice > > Is this correct? > > Any help would be gladly received. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
