[model].__str__() disagrees with __unicode__() using python3 / django1.5b1
|Reported by:||Owned by:||nobody|
|Severity:||Normal||Keywords:||str unicode admin|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
I created a few models, providing each with a unicode() method as described at  and in the admin area, when I look at a list of such objects, each is listed as [Class Name] object rather than the text representation defined in my unicode() methods.
I used python2.7 and got the expected results, I also defined str() to return self.unicode() and again got the expected results.
I assume this is something to do with python3's handling of unicode/byte-strings, but it seems to me that one of the following three is needed:
1) the str() function should continue to return the same text representation as the unicode() method unless overridden
2)the admin should use unicode() in place of str() - along with any other part of django
3) the docs should be updated to make it clear what I should do in this situation (I'll stick with defining str() to return the same as unicode() for now, but I'd rather not have to, DRY and all that...
NB eveywhere you see unicode(), the bug tracker software has helpfully converted my double underlines before and after the function name into underlining the function name - sorry!
Cheers & God bless
Sam "SammyTheSnake" Penny