ak wrote: > Bjorn, if you read my first messages and specially my patch #3370, you > find that I made a suggestion that if the guys want to move to unicode > they better drop all native encodings support and so does my patch.
With all due respect, you seem to not understand this. 'Unicode' does not mean 'dropping native encodings support'. This is just FUD. Your patch in #3370 is broken (as I showed to you in personal mail) because it 'encodes' __str__ which works only for your special case where you assign a unicode object to a model property and return it from __str__. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
