Hi Malcolm, Malcolm Tredinnick wrote: > It's a much tougher requirement on the developer. They have to change > every piece of their code. Instead, we can accept UTF-8 bytestrings or > unicode strings and large amounts of code will work unchanged. > > There aren't actually that many places where strings go back and forth > between Django and the developers code, so doing the conversion to > Unicode, if necessary, at the Django interface isn't appearing to be > that hard.
I'm not sure if this makes it really easier for the developers. If I understand you correctly, the developer gets back unicode strings in any case from Django. But as soon as the developer compares the unicode string to something else from his/her own code, or appends strings, or uses any of the other various python operators that implicitly convert in mixed unicode/bytestring operation, the operation will surprisingly fail when there's a non-ASCII character in the developer's bytestring. Though, I'm still not sure whether I really want a unicode-everywhere approach ... Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
