Documentation talks about __unicode__() which doesn't exist in Python 3.x anymore
|Reported by:||flabifabi@…||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Description (last modified by lukeplant)
On the above mentioned page, the tutorial tells me to write a __unicode__() method to get a human-readable representation of my object. I tried but it didn't work. I then found out that since I'm using Python 3.3 I have to define a method __ str __(). Since there's a block debating whether to use __str__() or __unicode__() anyways, may it would be useful to add a hint for Python 3.x users to always use __str__().