On Thu, Dec 27, 2012 at 7:15 PM, Aymeric Augustin < [email protected]> wrote:
> 2) under Python 2.x __str__ is implemented as __unicode__ > encoded to utf8. > > > Yes, this is a legacy behavior that I strongly disagree with. It > makes __str__ / __unicode__ handling for Model subclasses > exceedingly sketchy.* The only reason why I didn't remove > it is backwards compatibility. > I'm curious what would you do instead, if backward-incompatibility were not a concern? Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
