id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
4814	System Message within Tutorial 1: Why __unicode__() and not __str__()	eryost@…	anonymous	"I have been going through your tutorial lately and noticed a change from the use of __str__() to __unicode__() and read the new block with the text below:

----

Why __unicode__() and not __str__()?
    
    If you’re familiar with Python, you might be in the habit of adding __str__() methods to your classes, not __unicode__() methods.

'''System Message: WARNING/2 (<string>, line 499)
Block quote ends without a blank line; unexpected unindent.'''

We use __unicode__() here because Django models deal with Unicode by default. All data stored in your database is converted to Unicode when it’s returned.

----

Since the System Message listed above doesn't seem to be explained, I didn't think that it was the reason for a switch from __str__() to __unicode__(), but that there was something you had meant to include that had a problem.

I'm really impressed with Django - keep up the good work!"		closed	Documentation			fixed	tutorial1 __unicode__ __str__		Ready for checkin	1	0	0	0	0	0